ERA25LA371 · North American T-6G
North American T-6G · Accident: runway excursion during takeoff
From an unrecorded airport to Millington-Memphis Airport (NQA)
Event
- NTSB case
- ERA25LA371
- 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
- 0
- 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 T-6G
- Aircraft type
- North American T-6
- 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
- N888WV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Millington-Memphis Airport (NQA), Millington, TN
- Aircraft age
- About 74 years (built 1951)
- 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
- Runway excursion
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
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 of the vintage, tailwheel-equipped airplane was departing from a turf runway. The pilot described that as he initiated the takeoff toward the west, and into the setting sun, he looked inside the airplane to verify the engine instruments. It took his eyes several seconds to adjust to the shaded cockpit and when he next looked outside he was surprised to see that the airplane had drifted to the left and he was no longer able to see the runway edge markers. The airplane’s main landing gear then encountered a “dip” that ran alongside the runway and he was unable to apply corrective control inputs to bring the airplane back onto the runway. The airplane’s left wing subsequently struck a metal pole and trees, after which the airplane nosed over and caught fire. Bystanders extricated the pilot from the cockpit and the airplane’s wings, fuselage, and empennage were substantially damaged. A witness video of the takeoff showed that when the pilot began the takeoff roll, the airplane was not aligned with the runway and was oriented slightly left. As the engine power increased, the airplane veered further left. The airplane’s tailwheel was oscillating from side to side, and the rudder was visibly moving. Following the accident, the pilot could not recall whether he had locked the tailwheel prior to initiating the takeoff. Postaccident examination of the tailwheel assembly revealed that the tailwheel locking mechanism was locked, though it could not be determined whether this as-observed condition was consistent with the configuration during takeoff, had been engaged later during the accident sequence, or as the result of manipulation during the examination. Additionally, the tailwheel locking pin was broken into two pieces, with the upper half frozen into position in its guide while the lower half was worn. This condition would likely have resulted in the tailwheel lock operating unreliably, and with the tailwheel not properly locked, would have hampered any efforts the pilot would have made to realign the airplane with the runway after initiating the misaligned takeoff roll. Had the pilot confirmed the operation of the tailwheel locking mechanism prior to initiating the takeoff, it is possible that he could have recognized the deficiency and avoided the accident.
Probable cause
The pilot’s failure to adequately monitor the airplane’s path during takeoff toward the setting sun. Contributing was the undetected worn and fractured tailwheel locking pin.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA371
- Event ID
- 20250930201749
- Case number
- ERA25LA371
- 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, cause areas. 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: 717ad6fbf109d4162d6111f90821006944d97380df6d68f37508be9ed4fcb7dc; retrieved 2026-09-16T20:24:06.536Z.