FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA05LA165 · Cessna 120

6 Aug 2005 · Chiloquin, OR, United States

Cessna 120 · Accident: loss of control in flight during initial climb

From Chiloquin State Airport (2S7) to an unrecorded destination

Report a problem

Event

NTSB case
SEA05LA165
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 120

Aircraft type
Cessna 120
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
N627DM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chiloquin State Airport (2S7), Chiloquin, ORTo not recorded
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
Loss of control in flight
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
Stall/spin
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

  • Pilot in command › Airspeed, not maintained
  • Pilot in command › Pull-up, initiated

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Witnesses observed the airplane departing to the south. One witness reported seeing the airplane about 20 feet above the ground when it pulled up steeply, banked hard to the left, and then continued to turn and went straight into the ground. Other witnesses said that just after the airplane took off and was approximately 200 to 300 feet above the ground, it nosed down and impacted terrain. A postaccident examination revealed no anomalies with the airplane which would have precluded normal operations.

Probable cause

The pilot's failure to maintain airspeed and a loss of control during a pull-up maneuver. A factor contributing to the accident was the inadvertent stall/spin, which resulted in the subsequent collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA05LA165
Event ID
20050810X01199
Case number
SEA05LA165
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-08-07.
  • API snapshot SHA-256: 629c4b5f40ed6a74ecd7bb4cc89e5d9c5781a85e3f12de6006eb3521e1dae354; retrieved 2026-09-20T17:56:40.070Z.