Fatal error on export merge households under some circumstances

Steps to replicate
1) do a search & find some contacts
2) select export
3) choose merge households and configure an export set that includes Individual-street-address billing AND individual-city
4) error

Database Error Code: Column count doesn't match value count at row 1, 1136
Additional Details:

Array
(
[callback] => Array
(
[0] => CRM_Core_Error
[1] => handle
)

[code] => -22
[message] => DB Error: value count on row
[mode] => 16
[debug_info] =>
INSERT INTO civicrm_export_temp_c0877be4bcfe19aebd6e5b7a342c75dc (id, billing_street_address,billing_city,civicrm_primary_id,7_a_b_billing_street_address,7_a_b_billing_city,7_a_b_id,6_a_b_billing_street_address,6_a_b_billing_city,6_a_b_id)
VALUES (1,'','','631','','','','')
[nativecode=1136 ** Column count doesn't match value count at row 1]
[type] => DB_Error
[user_info] =>
INSERT INTO civicrm_export_temp_c0877be4bcfe19aebd6e5b7a342c75dc (id, billing_street_address,billing_city,civicrm_primary_id,7_a_b_billing_street_address,7_a_b_billing_city,7_a_b_id,6_a_b_billing_street_address,6_a_b_billing_city,6_a_b_id)
VALUES (1,'','','631','','','','')
[nativecode=1136 ** Column count doesn't match value count at row 1]
[to_string] => [db_error: message="DB Error: value count on row" code=-22 mode=callback callback=CRM_Core_Error::handle prefix="" info="
INSERT INTO civicrm_export_temp_c0877be4bcfe19aebd6e5b7a342c75dc (id, billing_street_address,billing_city,civicrm_primary_id,7_a_b_billing_street_address,7_a_b_billing_city,7_a_b_id,6_a_b_billing_street_address,6_a_b_billing_city,6_a_b_id)
VALUES (1,'','','631','','','','')
[nativecode=1136 ** Column count doesn't match value count at row 1]"]

Note that I have reproduced this on demo and our sites - and this is NOT related to CRM-14398 (ie I can replicate it on a site that does not have patches for that issue).

This does not manifest if ONLY street address or ONLY city are chosen but does affect other location types with the EXCEPTION of primary (which is why this bug is not experienced more often)