CEN22LA160 · Cessna 180
Cessna 180 · Accident: collision during takeoff/landing
From an unrecorded airport to Lakeview Airport (30F)
Event
- NTSB case
- CEN22LA160
- 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 180
- 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
- N4738B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Lakeview Airport (30F), Dallas, TX
- Aircraft age
- About 67 years (built 1955)
- 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
- Collision during takeoff/landing
- 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
- Tree(s)
- 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
- 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 tailwheel equipped airplane reported that when he landed, the landing was “rough” and right at the edge of the airplane’s crosswind capabilities. Due to the strong crosswind, the pilot said he thought he would be better off taking off into the wind from the perpendicular taxiway since it was more into the wind. He said that during the takeoff, the wind wasn’t as strong as he thought, and he wasn’t able to clear the trees that were in the departure path. A cell phone video of the accident provided by a witness was consistent with the pilot’s description of the accident. The airplane sustained substantial damage to the left elevator, right wing, and right aileron. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The accident airport had one runway (16/34) and the recorded winds about the time of the accident were from 300° at 12 kts, gusting to 25 kts.
Probable cause
The pilot’s decision to perform a takeoff from a perpendicular taxiway rather than the airport runway, which led to the airplane striking trees at the end of the departure path.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA160
- Event ID
- 20220331104862
- Case number
- CEN22LA160
- 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: d5c50ff3ff5a38538f3a7515c47d0a3a8d01dee1622361dce0b3bb2d2fa7c661; retrieved 2026-09-16T15:05:23.411Z.