FTW04FA025 · Beech A45
Texas Air Aces Beech A45 · Accident: airframe, component or system failure while maneuvering
From David Wayne Hooks Memorial Airport (DWH) to an unrecorded destination
Event
- NTSB case
- FTW04FA025
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Beech A45
- Aircraft type
- Beechcraft 45
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N44KK
- Operator
- Texas Air Aces
- Onboard fatalities
- Unknown
- Route
- From David Wayne Hooks Memorial Airport (DWH), Spring, TXTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Company/operator management › Improper use of equipment/aircraft
- Company/operator management › Maintenance, compliance with ad, not complied with
- Wing, spar › Failure, total
- Wing, spar › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While maneuvering in a simulated air-to-air combat scenario with another airplane, the accident airplane was in a climbing right turn when the right wing separated from the airframe. Subsequently, the airplane spun uncontrolled to the ground. The right wing was located approximately 1/2 mile north of the main wreckage. Examination of the separated wing revealed extensive fatigue cracking in both forward and aft wing spars. On July 9,1999, AD 99-12-02 was issued by the FAA mandating flight and operating limitations on all Beech A45 (T-34) aircraft until structural inspection procedures could be developed. The AD prohibited operations in acrobatic and utility categories, limited the flight load from to 2.5 "G's" and limited the maximum airspeed to 175 mph. Entries in maintenance logbooks indicated that AD 99-12-02 was accomplished on June 3,1999. A former customer of the operator had flown in the accident airplane in May, 2001, and recalled that during the flight, the instructor pilot told him that they pulled about positive 6 "G's." On August 16, 2001, the FAA issued AD 2001-13-18, which superseded AD 99-12-02, and required inspections of the wing spars for cracks per Raytheon Aircraft Company (RAC) mandatory Service Bulletin (SB) 57-3329. AD 2001-13-18 allowed the operator an alternative method of compliance (AMOC) or an adjustment to the compliance time if the method provides an "equivalent level of safety" to the AD. On November 13, 2001, the airplane underwent a 100-hour inspection at which time log entries indicated that paragraphs d(1), d(2), and d(3) of AD 2001-13-18 were complied with and that paragraphs d(5), d(6), and d(7) were complied with by August 2002. On August 26, 2002, at an aircraft total time of 8,031.4 hours, compliance with the remaining provisions of AD 2001-13-18, through the use of an AMOC, began with inspections of the rear spar bathtub fittings per the T-34 Technical Committee Report. No discrepancies were noted at this time. On December 16, 2002, the FAA issued a revised Special Airworthiness Information Bulletin (SAIB) number CE-02-38R2 to advise all operators to the available AMOCs for compliance with AD 2001-13-18. The aircraft then underwent two subsequent 100-hour inspections and an annual inspection with no work noted related to the AMOC. On November 5, 2003, the aircraft underwent a 100-hour inspection and entries in the logbook indicated that the mechanic called the FAA Aircraft Certification Office (ACO) in Wichita, Kansas, and inquired about a possible time extension to comply with AD and AMOC requirements. According to the logbook entry, the representative from the ACO informed the mechanic that "as long as the rear spar inspection was complied with that the aircraft could continue to fly but the limiations specified in AD 99-12-02 would remain until AMOC completed." In a written statement, the representative from the ACO stated that he received a telephone call concerning the T-34 wing AD and SAIB, regarding certain AMOC's. He reported that the operator informed him "that the aircraft was coming up on the two hundred hour limit specified in the SAIB and that the aircraft would be grounded because the replacement spar was not yet installed. The operator wanted to know what could be done to continue flying." The ACO representative further stated that he informed the operator to "perform the inspections required by the AD. This would permit the aircraft to continue flying until the mod could be completed." On November 5, 2003, the rear bathtub fitting inspection was again performed with no discrepancies noted, 220.5 hours since the first bathtub fitting inspection. No documentation of a scheduled AMOC modification was found in the aircraft logbook. According to available records, the aircraft had not completed any AMOC or the Raytheon Service Bulletin. The lower wing bathtub fitting had been inspected allowing operation beyond the 80-hour limit with restrictions, about 2 weeks prior to the accident. On March 15, 2004, the FAA published AD2001-13-18 R1, which rescinded all previously approved AMOC's for the T-34 wing. The new AD also grounded any T-34 that had not accomplished the Raytheon Service Bulletin, and had flown more than 80 hours since August 16, 2001. The FAA determined that the AMOC's listed in AD 2001-13-18 did not address all critical areas in the wing spar assembly, and should no longer be valid.
Probable cause
The non-compliance with applicable Airworthiness Directives which required wing spar inspections, and the continued operation of the aircraft beyond the compliance time extension granted as per the approved alternate means of compliance (AMOC). Also causal was the operation of the aircraft outside of its flight "G" load limitations. Contributing factors were the misunderstanding between the Federal Aviation Administration (FAA) ACO and maintenance personnel in regard to AD/AMOC compliance, the insufficient AMOC’s, and failure of the operator to adequately comply with CFR Part 91 subpart E, maintenance.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW04FA025
- Event ID
- 20031203X01988
- Case number
- FTW04FA025
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 6d99428b07a4c770530426b983f9408b63cdb19c782e0c9c85f01c208b828298; retrieved 2026-09-20T18:47:09.730Z.