SEA83LA101 · Mooney M20J
Competition Aircraft Mooney M20J · Accident: loss of control on ground/water during landing
From King County International Airport - Boeing Field (BFI) to Roche Harbor Airport (WA09)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- SEA83LA101
- 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
Mooney M20J Possible conflict
- Aircraft type
- Mooney M20
- 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
- N1143G
- Operator
- Competition Aircraft
- Onboard fatalities
- Unknown
- Route
- From King County International Airport - Boeing Field (BFI), Seattle, WATo Roche Harbor Airport (WA09), Blaine, 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 · flare/touchdown
- 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 on ground/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 › Compensation for wind conditions, improper
- Pilot in command › Directional control, not maintained
- Pilot in command › Ground loop/swerve, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING HIS FIRST APPROACH TO LAND, THE PLT INITIATED A GO-AROUND AFTER FLOATING TOO FAR DOWN THE RWY. HE REPORTED THAT THE SECOND APPROACH & LANDING WERE NORMAL UNTIL A FEW SECONDS AFTER TOUCHDOWN. AT THAT TIME, THE ACFT ENCOUNTERED A GUST OF WIND, LIFTED OFF & YAWED INTO THE WIND. IT IMMEDIATELY SETTLED TO THE RWY WHILE STILL ANGLED INTO THE WIND, THEN VEERED OFF THE RWY & COLLIDED WITH A PARKED ACFT. ACCORDING TO THE PLT, THE WIND WAS VARIABLE FROM 250 TO 270 DEG AT APRX 10 KTS. THERE WERE HIGH TREES ALONG THE LEFT SIDE OF RWY 32 WHICH SHIELDED THE FIRST 1/3 OF THE RWY FROM WINDS OUT OF THE WEST. APRX 18 MI AWAY AT BELLINGHAM, WA, THE 1300 PDT WIND WAS FROM 310 DEG AT 8 KTS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA83LA101
- Event ID
- 20001214X43151
- Case number
- SEA83LA101
- 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: f89719c7bed7b448825d73eda4cfce9ae7985bc3906b10888c584066cf6f15f7; retrieved 2026-09-23T22:13:48.183Z.