DFW06FA173 · Cessna 180K
Cessna 180K · Accident: in flight collision with object during initial climb
From Owasso, OK to Gundys Airport (O38)
Event
- NTSB case
- DFW06FA173
- 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
- 1 · 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 180K
- Aircraft type
- Cessna 180
- 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
- N1SE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Owasso, OKTo Gundys Airport (O38), Owasso, 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
- Initial climb
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, static
- 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 › Unsuitable terrain or takeoff/landing/taxi area, selected
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot mistakenly landed a single-engine tailwheel equipped airplane on a 1,600-foot long by 22-foot wide asphalt residential street, which was approximately 4,000 feet east of his reported destination runway, a 2,600-foot long by 26-foot wide asphalt runway. Both the intended runway and the street were oriented in a north-south direction, and terminated at the same east-west road. Also, both the intended runway and the residential street had orange windsocks situated east of their locations. During landing the airplane's left wing impacted a signpost which was located adjacent to the street. After a brief back taxi, the pilot attempted a takeoff on the street. Shortly after liftoff, the airplane drifted under two adjacent transmission lines. As it continued to climb, the left wing came up under, and slid along, the lower transmission line before the airplane rolled across the wires and impacted the ground in a near vertical descent. A postcrash fire erupted. An examination of the airframe and engine did not reveal any preimpact anomalies that would have prevented normal operation.
Probable cause
The pilot's selection of unsuitable terrain, a residential street, for both takeoff and landing, which resulted in a collision with a static wire and terrain during takeoff-initial climb.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06FA173
- Event ID
- 20060706X00883
- Case number
- DFW06FA173
- 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: 3e6b257d108657a783e371a1125b07fa68a189ad529f9394ae7d698ddfb03152; retrieved 2026-09-20T17:13:14.326Z.