FTW05LA003 · Lockheed 18-56
Commemorative Air Force Lockheed 18-56 · Accident: loss of control on ground/water during takeoff
From Midland International Air and Space Port (MAF) to 1V5 · Boulder, CO
Event
- NTSB case
- FTW05LA003
- 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
Lockheed 18-56
- Aircraft type
- Lockheed 18
- 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
- N6371C
- Operator
- Commemorative Air Force
- Onboard fatalities
- Unknown
- Route
- From Midland International Air and Space Port (MAF), Midland, TXTo 1V5 · Boulder, CO
- 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 · roll/run
- 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 18,000- hour pilot was cleared for takeoff in the vintage twin-engine tail wheel equipped airplane on a 9,501- foot by 50- foot runway. The pilot was aware that there was a tailwind from approximatly 160 degrees at 10 knots. Shortly after starting the takeoff roll, the airplane swerved to the right. The pilot was able to correct back to the centerline utilizing rudder control. The airplane then swerved to the left, and full right rudder was applied but the swerve could not be corrected. By the time the airplane reached the left edge of the runway, the airplane had not reached its calculated V2 speed of 110 knots. The airplane departed the left side of the runway, went airborne and shortly thereafter, the right wing dropped and contacted the ground. The airplane then spun 180 degrees, impacted the ground, slid backward, and came to rest upright. A post-crash fire consumed the aft fuselage and left wing.
Probable cause
The pilot's failure to maintain directional control during takeoff. Contributing factors were the choice of runway used and the prevailing tailwind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW05LA003
- Event ID
- 20041007X01590
- Case number
- FTW05LA003
- 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: 0394fe6693dafbabb9226cae408d6d8ff351e2ae5604fbe72773f617b19312e8; retrieved 2026-09-21T19:07:37.798Z.