- Date
- March 2, 1968
- Place
- Glendale, AZ · GLENDALE, AZ
- Injuries
- 1 serious
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N4421Travel Air 4000
- Status
- Completed · report March 24, 1970
- Report
- Brief approved by the director
- Case key
- 111578
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-4927 68/3/2 GLENDALE,ARIZ TRAVEL AIR 4000 CR- 0 1 0 COMMERCIAL COMMERCIAL, AGE 48, 11000 TIME - 1134 N4421 PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 7000 IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - FRAM DEPARTURE POINT INTENDED DESTINATION GLENDALE,ARIZ GLENDALE,ARIZ TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: EN ROUTE TO TREAT CROP STALL LANDING: FINAL APPROACH PROBABLE CAUSE(S) POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 7000 KIND OF OPERATION - FERTILIZING (DUST) KIND OF CROP - GRAIN FIELDS TYPE OF CHEMICAL USED - UNKNOWN/NOT REPORTED PILOT' S SEAT BELT -FASTENED-PROPERLY CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT
Aircraft
- Registration
- N4421
- Reported as
- Travel Air 4000
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Fram
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.