DFW05CA248 · Piper PA-46T
Piper PA-46T · Accident: hard landing en route
From Wiley Post Airport (KPWA) to an unrecorded destination
Event
- NTSB case
- DFW05CA248
- 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
Piper PA-46T
- Aircraft type
- Piper PA-46
- 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
- N7WS
- Operator
- Robert N. Barnes · private individual
- Onboard fatalities
- Unknown
- Route
- From Wiley Post Airport (KPWA), Oklahoma City, OKTo not recorded
- 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
- En route · descent
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 1,576-hour private pilot was on an instructional training flight with his flight instructor practicing emergency procedures. A simulated power-off emergency descent was initiated by the flight instructor at 5,000 feet mean sea level (MSL) over the airport. The pilot successfully descended and aligned the airplane for final approach to Runway 17 when "an excessive sink rate developed on short final." The flight instructor directed the pilot to initiate a go-around. According to the pilot's statement in the NTSB Pilot/Operator Aircraft Accident Report (NTSB form 6120.1/2) he "immediately initiated the go-around by adding power; however the long engine spool-up time led to a hard landing/touch and go." Weather at the time of the accident was reported to be, winds at 210 degrees and 9 knots, visibility 10 statute miles, temperature 75 degrees Fahrenheit, altimeter 29.93 inches of Mercury.
Probable cause
The improper flare which resulted in a hard landing. A related factor was the instructor's delayed remedial action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05CA248
- Event ID
- 20051130X01912
- Case number
- DFW05CA248
- 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: 8161a6b1f10223bce46b5d47474476e026d09ebe2f1163ec541ba4cd52cbebaa; retrieved 2026-09-22T05:21:01.168Z.