Currently, addresses of family accounts are not updated in the NCOA run; it only works for individual and business accounts.

Per eTapestry support, the NCOA bases family accounts off the last name.  However, because eTapestry does not have a last name field for family accounts, it cannot compare the last name in the NCOA database to the name in eTapestry. For this reason, the AddressFinder service in eTapestry will standardize the family addresses (for example, it will shorten "Street" to "St" per the Post Office's standards), but it will not be able to locate a new address for family accounts.

Could the eTapestry development team parse the last name from the Account Name or Sort Name field for family accounts and then use that parsed field to compare to the NCOA database?  This would greatly increase the number of address changes processed for family accounts (which comprise 1/3 of our total donor base but are often our most active donors).