- Date
- May 6, 1971
- Place
- Coolidge, AZ · COOLIDGE, AZ
- Injuries
- 12 fatal
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N4922VDehavilland 104-7X
- Status
- Completed · report August 17, 1972
- Safety recommendations
- Yes
- Case key
- 79655
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-0038 71/5/6 COOLIDGE,ARIZ DEHAVILLAND 104-7X CR- 2 0 0 COMMERCIAL COMMERCIAL, AGE 31, 6000 TIME - 1315 N4922V PX- 10 0 0 COMMUTER AIR CARRIER TOTAL HOURS, 2500 IN DAMAGE-DESTROYED OT- 0 0 0 AIR TAXI-PASSG S-D TYPE, INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION TUCSON,ARIZ PHOENIX,ARIZ TYPE OF ACCIDENT PHASE OF OPERATION AIRFRAME FAILURE: IN FLIGHT IN FLIGHT: NORMAL CRUISE COLLISION WITH GROUND/WATER: UNCONTROLLED IN FLIGHT: UNCONTROLLED DESCENT PROBABLE CAUSE(S) AIRFRAME - WINGS: WING ATTACHMENT FITTINGS,BOLTS MISCELLANEOUS ACTS,CONDITIONS - FATIGUE FRACTURE MISCELLANEOUS ACTS,CONDITIONS - CORRODED/CORROSION PERSONNEL - PRODUCTION-DESIGN-PERSONNEL: POOR/INADEQUATE DESIGN PERSONNEL - PRODUCTION-DESIGN-PERSONNEL: SUBSTANDARD QUALITY CONTROL FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - SEPARATION IN FLIGHT FIRE AFTER IMPACT REMARKS- R WING LWR ATTACH FITTING FRACTURED DUE FATIGUE WHICH PROPAGATED IN AREA OF CORROSION AND FRETTING
Aircraft
- Registration
- N4922V
- Reported as
- Dehavilland 104-7X
- Category
- Airplane
- Engine
- turbo prop
- Damage
- Destroyed
N4922VRegistration cancelled Jul 8, 1971 · Dehavilland DH104 DOVE 7AXCAirframe modelDehavilland DH104 DOVE 7AXC
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.