- Date
- June 15, 1974
- Place
- Superior, WI · SUPERIOR, WI
- Injuries
- 2 minor, 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N56303Piper PA-28
- Status
- Completed · report September 10, 1974
- Report
- Brief approved by the director
- Case key
- 130207
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-2242 74/6/15 SUPERIOR,WIS PIPER PA-28 CR- 0 0 1 NONCOMMERCIAL PRIVATE, AGE 45, 84 TOTAL TIME - 0840 N56303 PX- 0 0 2 PLEASURE/PERSONAL TRANSP HOURS, 7 IN TYPE, NOT DAMAGE-SUBSTANTIAL OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - BONG DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP WEST CHICAGO,ILL ELY,MINN DULUTH,MINN TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION LANDING: GO-AROUND COLLIDED WITH: WIRES/POLES LANDING: FINAL APPROACH PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION PILOT IN COMMAND - IMPROPER IN-FLIGHT DECISIONS OR PLANNING MISCELLANEOUS ACTS,CONDITIONS - POORLY PLANNED APPROACH FACTOR(S) TERRAIN - HIGH OBSTRUCTIONS PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING ON AIRPORT/SEAPLANE BASE/HELIPT. REMARKS- OVERSHOT 1ST APCH.ACFT TOO LOW & TOO FAR FRM RWY WHEN ENG FAILED.
Aircraft
- Registration
- N56303
- Reported as
- Piper PA-28
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Bong
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.