- Date
- September 10, 1972
- Place
- White Marsh, MD · WHITE MARSH, MD
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N5612ZPiper PA-22
- Status
- Completed · report December 19, 1972
- Report
- Brief approved by the director
- Case key
- 111937
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-0804 72/9/10 WHITE MARSH,MD PIPER PA-22 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 33, 83 TOTAL TIME - 1635 N5612Z PX- 0 0 1 PLEASURE/PERSONAL TRANSP HOURS, 63 IN TYPE, NOT DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - BALTIMORE AIRPARK DEPARTURE POINT INTENDED DESTINATION PRESTON AIRPORT,NJ WHITE MARSH,MD TYPE OF ACCIDENT PHASE OF OPERATION OVERSHOOT LANDING: LEVEL OFF/TOUCHDOWN GEAR COLLAPSED LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS FACTOR(S) PERSONNEL - MAINTENANCE,SERVICING,INSPECTION: INADEQUATE MAINTENANCE AND INSPECTION AIRFRAME - LANDING GEAR: BRAKING SYSTEM (NORMAL SYSTEM) MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE REMARKS- BOTH BRAKE DISCS RUSTED,PITTED.R OUTBRD BRAKE LINING MISSING.WHEELBARROWED,NOSE GR COLLAPSED
Aircraft
- Registration
- N5612Z
- Reported as
- Piper PA-22
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Baltimore Airpark
N5612ZRegistration cancelled Feb 21, 2013 · Piper PA-22-108Airframe modelPiper PA-22-108Engine modelLycoming 0-235 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.