WPR19LA196 · Cessna 210 5(205) Undesignat
Cessna 210 5(205) Undesignat · Accident: abnormal runway contact during takeoff
From Columbia Gorge Regional Airport (DLS) to Columbia Gorge Regional Airport (DLS)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR19LA196
- 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
Cessna 210 5(205) Undesignat
- Aircraft type
- Cessna 210
- 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
- N8260Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Columbia Gorge Regional Airport (DLS), The Dalles, ORTo Columbia Gorge Regional Airport (DLS), The Dalles, OR
- Aircraft age
- About 55 years (built 1964)
- 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 · rejected 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
- Abnormal runway contact
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Not determined › Not determined
- 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
During the takeoff roll, the pilot noted that there was no airspeed indication and reduced engine power to abort the takeoff. He stated that he lightly pulled back on the yoke, felt the airplane lift off the runway and that he then released the yoke. The airplane porpoised “3 possibly 4” times, “with each getting larger” until the nose landing gear collapsed, and the airplane slid down the runway, coming to rest on the runway surface. As the pilot exited the airplane, he noted flames near the door. The airplane was subsequently consumed by fire. Postcrash fire damage precluded examination of the pitot-static system or airspeed indicator, and the reason for the lack of airspeed indication during the takeoff roll could not be determined.
Probable cause
The pilot’s improper pitch control during the aborted takeoff, which resulted in a bounced landing and landing gear collapse.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19LA196
- Event ID
- 20190721X34740
- Case number
- WPR19LA196
- 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: 04077b3d8b23c53f8acf1c71082d6b9ba4ca516384a824f0afb027f9e556dc7a; retrieved 2026-09-16T09:29:05.881Z.