- Date
- October 19, 1969
- Place
- Andrews Afb, MD · ANDREWS AFB, MD
- Injuries
- 1 minor, 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N7026DPiper PA-22
- Status
- Completed · report May 19, 1970
- Report
- Brief approved by the director
- Case key
- 152797
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-4217 69/10/19 ANDREWS AFB,MD PIPER PA-22 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 23, 133 TIME - 1850 N7026D PX- 0 0 2 PLEASURE/PERSONAL TRANSP TOTAL HOURS, 51 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - ANDREWS A.F.B. DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP NASHUA,NH P.G.AIRPARK,MD BRAINARD FLD,CONN TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION LANDING: FINAL APPROACH COLLIDED WITH: DITCHES LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - MISCALCULATED FUEL CONSUMPTION MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- FUEL NOT CHECKED DURG STOP AT BRAINARD.
Aircraft
- Registration
- N7026D
- Reported as
- Piper PA-22
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Andrews A.F.B.
N7026DRegistered now · Piper PA-22-150Airframe modelPiper PA-22-150Engine modelLycoming 0-320 series
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.