SEA90FA183 · Cessna 172-P
Wings Aloft Cessna 172-P · Accident: loss of control in flight during landing
From DLS · THE DALLES, WA to King County International Airport - Boeing Field (BFI)
Event
- NTSB case
- SEA90FA183
- 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
- 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 172-P
- Aircraft type
- Cessna 172
- 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
- N5332K
- Operator
- Wings Aloft
- Onboard fatalities
- Unknown
- Route
- From DLS · THE DALLES, WATo King County International Airport - Boeing Field (BFI), Seattle, WA
- 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(vs), not maintained
- Pilot in command › Spatial disorientation
- Pilot in command › Stall/spin, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE RECENTLY CERT PRIVATE PILOT WHO WAS NOT RATED FOR INST FLT TOOK OFF AT NIGHT ON A VFR X-COUNTRY FLT INTO AN AREA OF KNOWN IMC WX. WHEN THE FLT ENCOUNTERED ADVERSE WX, THE PILOT REVERSED COURSE AND ATTEMPTED TO LAND AT AN UNFAMILIAR ARPT. THE ACFT TOUCHED DOWN LONG AND THE PILOT ANNOUNCED ON UNICOM THAT HE WAS MAKING A GO-AROUND. THE ACFT CLIMBED TO ABOUT 200 FT AGL, STALLED AND DESCENDED NOSE DOWN UNTIL IT IMPACTED THE GROUND. SKY WAS OVERCAST AND MODERATE RAIN WAS FALLING. THERE WAS NO ARTIFICIAL LIGHT IN THE DIRECTION OF FLT. THE PILOT HAD 5 HRS NIGHT TIME AND NONE OUTSIDE A LIGHTED METRO AREA.
Probable cause
THE PILOT IN COMMAND'S ENCOUNTERING SPATIAL DISORIENTATION AND HIS FAILURE TO MAINTAIN AIRSPEED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA90FA183
- Event ID
- 20001212X24365
- Case number
- SEA90FA183
- 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 1990-09-16.
- API snapshot SHA-256: a03604383a2716ba70cb18f594a1c8326a2afc17e550c12a9427d7a9dc9341e4; retrieved 2026-09-21T02:12:00.713Z.