ERA11FA293 · Beech F33A
Jon Air Beech F33A · Accident during takeoff
From Pittsburgh Northeast Airport (9G1) to Pittsburgh Northeast Airport (9G1)
Event
- NTSB case
- ERA11FA293
- 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
Beech F33A
- Aircraft type
- Beechcraft 33
- 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
- N17825
- Operator
- Jon Air
- Onboard fatalities
- Unknown
- Route
- From Pittsburgh Northeast Airport (9G1), Tarentum, PATo Pittsburgh Northeast Airport (9G1), Tarentum, 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
- Defining eventThe 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
- Unknown or undetermined
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to passengers, the airplane began its takeoff roll at the approach end of the runway, accelerated, lifted off, climbed a few feet, and settled back on the runway. The airplane "swerved" as it slowed and then overran the departure end of the runway and 100 feet of the grass overrun area. Skid marks were observed about 712 feet before the end of the runway. Postaccident examination of the wreckage revealed no preimpact mechanical anomalies. The engine was test run and it operated satisfactorily. Weight and balance calculations revealed the estimated weight of the airplane at takeoff was 3,830 pounds, which was 230 pounds above the maximum allowable gross weight. The accelerate/stop distance calculated for the airplane’s takeoff weight was 2,483 feet. Based on the length of the runway and the calculated accelerate/stop distance, the pilot should have been able to abort the takeoff in time to avoid an overrun.
Probable cause
The pilot's delay in aborting the takeoff, which resulted in a runway overrun. Contributing to the accident was the pilot's inadequate preflight planning and excessive loading of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11FA293
- Event ID
- 20110511X35743
- Case number
- ERA11FA293
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: f01c036a00d429eef29ee992bde1262417c55b88d8d3d6004fffe6bd30828301; retrieved 2026-09-15T16:09:18.965Z.