NYC03LA034 · SOCATA TB 9
SOCATA TB 9 · Accident: overrun during takeoff
From MUU · Mount Union, PA to York Airport (THV)
Event
- NTSB case
- NYC03LA034
- 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
- Unknown
- 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
SOCATA TB 9
- Aircraft type
- Socata TB-9
- 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
- N136ER
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From MUU · Mount Union, PATo York Airport (THV), York, 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
- Takeoff · rejected takeoff
- 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
- Overrun
- 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 › Aborted takeoff, delayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was departing on runway 22, a 3,120-foot long, 80-foot wide, gravel and turf runway. The runway was "soft and soupy," and the airplane did not accelerate properly. The pilot was able to lift two of the landing gear off the runway, but the airplane would not become airborne. The pilot further stated that the accident airplane usually became airborne after a ground roll of about 500 feet, on a paved runway with only one person on board. During the accident takeoff, the wheels didn't begin to break ground until approximately 1,000 beyond the approach end of the runway. The pilot decided to abort the takeoff about 1,600 feet beyond the approach end of the runway. However, the airplane skid on the soft ground, overran the runway at a speed of approximately 35-45 knots and came to rest inverted in a ditch. The pilot added that there were no pre-impact mechanical malfunctions with the airplane.
Probable cause
The pilot's delay in aborting the takeoff. A factor was the soft runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC03LA034
- Event ID
- 20030107X00029
- Case number
- NYC03LA034
- 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: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: ba47020981261cf3a9403644755770a6f124df9d77547353ac209ac4644adf6b; retrieved 2026-09-22T09:44:42.293Z.