NYC83LA096 · Mitsubishi MU-2B-26
Mitsubishi MU-2B-26 · Accident: hard landing
From W07 · Fredericksburg, VA to Allegheny County Airport (AGC)
Event
- NTSB case
- NYC83LA096
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Mitsubishi MU-2B-26
- Aircraft type
- Mitsubishi MU-2
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N79AC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From W07 · Fredericksburg, VATo Allegheny County Airport (AGC), West Mifflin, PA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Flare, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACCORDING TO THE PILOT, HE INCREASED THE POWER, AND SUBSEQUENTLY THE AIRSPEED, WHILE ON FINAL APPROACH, TO COMPENSATE FOR STRONG WINDS AND TURBULENCE. THE WIND WAS REPORTED TO BE FROM 150 DEG. AT 18 GUSTING 28 KTS. REPORTEDLY, THE ACFT CROSSED OVER THE THRESHOLD OF RWY 10 AT AN AIRSPEED THAT WAS 30 KTS FASTER THAN NORMAL. THE PLT STATED THE ACFT LANDED HARD ON THE LEFT MAIN GEAR FIRST, THEN BEGAN TO LEAN TO THE LEFT. AT SOME POINT, THE LEFT PROPELLER HIT THE RWY AND SPARKS FLEW. THE PLT STATED THAT HE THEN PULLED UP THE ACFT, RETRACTED THE GEAR, SHUT DOWN BOTH ENGINES AND LANDED GEAR UP. AN EXAM REVEALED THAT THE TIPS OF THE LEFT PROPELLER HAD SHEARED OFF AND PENETRATED THE LEFT TIP TANK. ALSO, THE BELLY, GEAR DOORS AND LANDING GEAR WERE DAMAGED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83LA096
- Event ID
- 20001214X42810
- Case number
- NYC83LA096
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1983-04-15.
- API snapshot SHA-256: c0ec460f5b2419f396552e44e3bb1e7e4815e251f9f0fdbd8a2a7fc092de113e; retrieved 2026-09-23T22:24:49.036Z.