NYC06CA098 · Cessna 310Q
Cessna 310Q · Accident: undershoot on approach
From Rostraver Airport (FWQ) to Finleyville Airpark (G05)
Event
- NTSB case
- NYC06CA098
- 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 310Q
- Aircraft type
- Cessna 310
- 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
- N93AC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rostraver Airport (FWQ), Rostraver, PATo Finleyville Airpark (G05), Finleyville, 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
- Approach · VFR pattern final
- 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
- Undershoot
- 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 › Distance/speed, misjudged
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 was flying a visual approach to runway 32, a 2,505-foot long, 50-foot wide, asphalt runway. On final approach, the pilot had the airplane configured with flaps extended 15 degrees, the landing gear extended, manifold pressure 18 inches, and airspeed at 118 mph. About 700 feet from the runway threshold, he extended the flaps to 35 degrees, and decreased the airspeed to 100 mph. The airplane then started to sink, and the pilot added full power; however, the airplane touched down hard in a dirt field about 100 feet prior to the runway threshold. The airplane subsequently sustained substantial damage and came to rest upright, on a grass area off the right side of the runway. The reported wind at a nearby airport, about the time of the accident, was from 320 degrees at 13 knots, gusting to 18 knots. The pilot did not report any pre-impact mechanical malfunctions with the airplane.
Probable cause
The pilot's misjudged distance/speed during final approach, which resulted in an undershoot and hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06CA098
- Event ID
- 20060504X00504
- Case number
- NYC06CA098
- 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: b97ab782e29368e16f9b5cc86b4ef62ead236da2fa131e0bb399dc0f5da4a16e; retrieved 2026-09-22T04:59:36.749Z.