NYC05LA067 · Cessna 182S
Pittsburgh Flight Training Center Cessna 182S · Accident: loss of control on ground/water during takeoff
From Allegheny County Airport (AGC) to Allegheny County Airport (AGC)
Event
- NTSB case
- NYC05LA067
- 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
Cessna 182S
- Aircraft type
- Cessna 182
- 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
- N9521F
- Onboard fatalities
- Unknown
- Route
- From Allegheny County Airport (AGC), West Mifflin, PATo Allegheny County Airport (AGC)
- 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
- 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
- Loss of control on ground/water
- 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 › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was departing from runway 28, a 6,501-foot long, 150-foot wide, asphalt runway. The pilot reported that the initial takeoff roll was normal; however, the yoke felt extremely heavy and stiff. The airplane lifted off the runway, but it then bounced and contacted the runway in a nose down position. The nose gear collapsed, and the airplane slid to a stop. Examination of the airplane did not reveal any mechanical malfunctions. The elevator trim cable chain was separated; however, the trim cable was properly oriented and the trim tab moved appropriately when the respective trim cable was pulled by hand. Due to impact damage, and the separated trim cable chain, the airplane's pitch trim setting during the takeoff could not be confirmed. The pilot reported 190 hours of total flight experience, which included 27 hours in the same make and model as the accident airplane. Winds reported at the airport, about the time of the accident, were from 260 degrees at 8 knots, gusting to 20 knots.
Probable cause
The pilot's failure to maintain aircraft control during the takeoff. A factor in this accident was the gusty wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC05LA067
- Event ID
- 20050427X00508
- Case number
- NYC05LA067
- 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: e181ed4212f783f79054a2a7c519f43988c31e59d6fcac5cc4056ee5c0e4f925; retrieved 2026-09-22T06:06:43.586Z.