{"database": "openregs", "table": "comment_collisions", "rows": [[29, "FAA-2007-28478-0052", 1, "union_alias", "80384a2d", "2007-09-24T04:00:00Z", 0, "James Zangger ", "Background:  Service letter issued April of 2007 to address corrosion\n             issues identified in struts.  Origin and history of\n             suspect struts is undocumented.  Maintenance practices\n             associated with suspect aircraft are also undocumented.\n             Intent was to prevent in flight failures of struts.\n\nAD Issuance: Timing of AD appears to have been prompted by an\n             unrelated failure of a separate structure.\n\nHistory:     Taylorcraft has no documented record of in flight\n             structural failures until the recent Washington state\n             fatality.\n\n             (The accident aircraft was licensed in the experimental\n             category, annual inspections had been performed and\n             signed off by the owner IA, aircraft was stored outdoors\n             on a lake in a salt air environment while on floats.\n             Condensation would develop in locations in a float\n             equipped airplane that may not apply to a land based\n             aircraft.)\n\nSafety:      Service letter was sufficient to inform owners of\n             problem areas.\n\n             (Distribution of the service letter was not consistent\n             and did not reach all owners.)\n\nMaintenance: Annual inspections using normal maintenance practices\n             have, over the years, found suspect areas.  Appropriate\n             repairs have been made to allow the continued safe\n             flight of the aircraft.\n\nInspection:  Per the AD, the authorized inspections and frequency\n             of such to determine the presence of corrosion are\n             prohibitively expensive and unnecessarily repetitive.\n\nRecommendations:  Allow Alternate Means of Compliance that have been\n             approved on previous AD's of other aircraft -\n             specifically, the Maule test allowed on Piper struts.\n             This test would indicate whether the need for more\n             extensive testing is required.  A visual boroscope\n             inspection would also identify any corrosion on the\n             interior of the struts dictating the need for more\n             extensive testing.\n\n             While ultrasound inspections are able to accurately\n             determine wall thickness, the eddy current inspection\n             appears to be more appropriate on aluminum.  An x-ray\n             inspection would possibly be more revealing than either\n             of these other methods and be the correct test for any\n             future corrosion concerns in other areas.  This would\n             prevent the need for fabric removal in those areas.\n\n             If a structure is determined to have no corrosion\n             through the use of these test methods, the frequency\n             of re-inspection bi-annually seems unnecessary.  Logic\n             would dictate that if no corrosion had occured in 60\n             years or more that little new corrosion would form in\n             the next two years, certainly not enough to raise \n             concern over the integrity of the material.\n\n             Wouldn't it be reasonable to test a suspect strut to\n             destruction as a means to determine if the strut meets\n             the original design load criteria?  This would allow a\n             determination as to what would be acceptable levels of\n             corrosion in a particular structure.\n", null, null, null, null, "FAA-2007:2007-01-01:2007-12-31"]], "columns": ["rowid", "id", "occurrence", "disposition", "tracking_number", "posted_date", "is_withdrawn", "title", "comment_text", "reason_withdrawn", "attachment_files", "content_files", "duplicate_comments", "source_slice"], "primary_keys": ["rowid"], "primary_key_values": ["29"], "units": {}, "query_ms": 0.23966911248862743, "source": "Federal Register API & Regulations.gov API", "source_url": "https://www.federalregister.gov/developers/api/v1", "license": "Public Domain (U.S. Government data)", "license_url": "https://www.regulations.gov/faq"}