FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW08CA200 · Curtiss-Wright 12Q

27 Jul 2008 · Erie, CO, United States

Curtiss-Wright 12Q · Accident: system/component malfunction/failure (non-power) during landing

From Erie Municipal Airport (EIK) to Erie Municipal Airport (EIK)

Report a problem

Event

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

Curtiss-Wright 12Q

Aircraft type
Curtiss Wright 12
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
N496W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Erie Municipal Airport (EIK), Erie, COTo Erie Municipal Airport (EIK), Erie, 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
Landing · landing roll
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
System/component malfunction/failure (non-power)
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 systems

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The commercial pilot was returning from a local flight in his vintage single-engine, bi-wing airplane, which was equipped with a tail wheel. He said the winds were light and variable when he made a normal landing on the asphalt runway. However, during the landing roll-out, the airplane suddenly entered a left turn and the pilot was unable to correct with right rudder and brake. The airplane entered the grass area adjacent to the runway, dragging its right wing tip, before it came to rest up on its nose. Examination of the airplane by an FAA inspector revealed that the tail wheel control cable had disconnected from the spring on the right side, which caused the left side spring to pull the tail wheel to the left. In addition, two ribs in the lower right wing were broken.

Probable cause

Failure of the tail wheel control cable during landing roll out, which resulted in a loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW08CA200
Event ID
20080909X01420
Case number
DFW08CA200
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: a79b0d945a453f07840a12b03b110a529e3c5b85486a008f19c9a873352e5c8c; retrieved 2026-09-15T10:11:02.108Z.