FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW08CA202 · North American P-51D

29 Jul 2008 · Tulsa, OK, United States

North American P-51D · Accident: loss of engine power (total) during takeoff

From Tulsa Riverside Airport (RVS) to Tulsa, OK

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's registration. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
DFW08CA202
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

North American P-51D

Aircraft type
North American P-51
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
N551w Narrative disagrees
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tulsa Riverside Airport (RVS), Tulsa, OKTo Tulsa, OK
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
Loss of engine power (total)
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 › Task performance

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 began his takeoff roll on a maintenance test flight. During the ground roll and near rotation speed, the pilot moved his hand from the throttle to the gear handle. The pilot reported that the throttle friction lock was not properly set and the throttle experienced "throttle creep" reducing engine power. The pilot advanced the throttle, at which time the airplane became airborne and began to torque roll. An aborted takeoff was executed by the pilot and the airplane touched down off of the runway. The airplane came to rest after contacting the airfield perimeter fence. Substantial damage was sustained to the right wing and left horizontal stabilizer.

Probable cause

The pilot's failure to maintain aircraft control during takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW08CA202
Event ID
20080903X01367
Case number
DFW08CA202
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, 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: b8dc065ccb6f548ed9114063b14dac10b2c558d9f7b4fa51b2091d2cf9184bb0; retrieved 2026-09-15T10:08:37.396Z.