SEA93LA066 · Cessna 120
Cessna 120 · Accident: loss of control in flight during landing
From 0S6 · Orchards, WA to an unrecorded destination
Event
- NTSB case
- SEA93LA066
- 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
- 0
- 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
- N2100V
- Operator
- Wills, Charles R. · private individual
- Onboard fatalities
- Unknown
- Route
- From 0S6 · Orchards, WATo 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
- Landing · aborted
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT ATTEMPTED TO LAND TO THE WEST ON A 1300 FOOT TURF AIRSTRIP. THE WEST EDGE OF THE AIRSTRIP TERMINATED IN POWER LINES AND TREES ESTIMATED TO BE 80 FEET TALL. A SINGLE WHEEL TRACK WAS OBSERVED BEGINNING 405 FEET FROM THE WEST EDGE OF THE STRIP AND PROGRESSING 45 FEET. A WITNESS STATED THAT HE 'SAW THE PLANE GO UP AND OVER THE TREES' AND THEN THE AIRCRAFT 'WENT STRAIGHT UP AND STALLED' AFTER WHICH IT 'ROLLED OVER A COMPLETE 180 DEGREE TURN AND LANDED ON ITS NOSE.' THE WITNESS REPORTED STRONG WINDS AT THE TIME OF THE ACCIDENT AND SURFACE WIND OBSERVATIONS AT PORTLAND INTERNATIONAL AIRPORT 13 NAUTICAL MILES SOUTHEAST WERE FROM 090 DEGREES IN THE TEENS WITH GUSTS IN THE 30'S.
Probable cause
THE PILOT IN COMMAND'S ALLOWING THE AIRCRAFT TO ENTER A STALL/SPIN CONDITION. FACTORS CONTRIBUTING TO THE ACCIDENT WERE A TAILWIND, POWER LINES AND TREES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA93LA066
- Event ID
- 20001211X11891
- Case number
- SEA93LA066
- 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. 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: a17982e72109b0ab928c2f241461d20a522da72ad9379bd72d83b165a4ab4571; retrieved 2026-09-21T14:33:11.960Z.