- Date
- January 12, 1973
- Place
- Noblesville, IN · NOBLESVILLE, IN
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N555CMitsubishi MU-2B
- Status
- Completed · report April 6, 1973
- Report
- Brief approved by the director
- FAA report
- 19730112000669A
- Case key
- 169654
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-0214 73/1/12 NOBLESVILLE,IND MITSUBISHI MU-2B CR- 0 0 1 MISCELLANEOUS COMMERCIAL, FL.INSTR., TIME - 1957 N555C PX- 0 0 1 FERRY AGE 38, 7327 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 5 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - INDIANAPOLIS DEPARTURE POINT INTENDED DESTINATION SPRINGFIELD,ILL MUNCIE,IND TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION LANDING: ROLL GROUND-WATER LOOP-SWERVE LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL STARVATION MISCELLANEOUS ACTS,CONDITIONS - THRUST REVERSAL-ASYMETRICAL COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING ON AIRPORT LOW ON FUEL REMARKS- REVERSED ENGS. R ENG FLAMED OUT AND L ENG WENT INTO REVERSE. VEERED OFF RWY. UNPLANNED STOP.
Aircraft
- Registration
- N555C
- Reported as
- Mitsubishi MU-2B
- Category
- Airplane
- Engine
- turbo prop
- Damage
- Substantial damage
- Airport
- Indianapolis
N555CRegistration cancelled Jun 14, 2012 · Mitsubishi MU-2B-20Airframe modelMitsubishi MU-2B-20Engine modelAiResearch 331 SER 605HP
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.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.