SEA06LA076 · Cessna 180
Cessna 180 · Accident: on ground/water collision with terrain/water during landing
From Crater Lake-Klamath Regional Airport (KLMT) to Crater Lake-Klamath Regional Airport (KLMT)
Event
- NTSB case
- SEA06LA076
- 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
- N40LT
- Operator
- Claren Nilsson
- Onboard fatalities
- Unknown
- Route
- From Crater Lake-Klamath Regional Airport (KLMT), Klamath Falls, ORTo Crater Lake-Klamath Regional Airport (KLMT), Klamath Falls, OR
- 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
- 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
- On ground/water collision with terrain/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
After her initial departure, the pilot flew about 10 minutes south to another airport, where she executed about 10 touch-and-go landings. When the winds started to become variable and gusty at this location, the pilot returned to her initial departure point where she was cleared for a full-stop landing on runway 32. Although the touchdown was uneventful, according to the pilot, during the landing roll a crosswind gust lifted the left wing, and the aircraft began to veer from the runway heading. During her attempt to realign the aircraft with the runway, it turned sharply to the left, and the right wing and right elevator came in contact with the runway surface. The pilot said there did not appear to be any problems with the aircraft's flight controls or tailwheel steering system. After she taxied to parking, the pilot talked to an individual who had landed just before her, and that individual stated that he had also encountered gusty crosswinds. The two pilots estimated the gusts were as high as 15 knots.
Probable cause
The pilot's failure to maintain directional control of the tailwheel-equipped aircraft during the landing roll. Factors include gusty crosswinds.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA06LA076
- Event ID
- 20060420X00465
- Case number
- SEA06LA076
- 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: 8ae8e32de45b11b31ef2e9be63171889215cd14ab31b8d60c6827415fc1715c0; retrieved 2026-09-22T04:59:46.748Z.