SEA02FA106 · Consolidated Aeronautics Inc. LA-4-200
Consolidated Aeronautics Inc. LA-4-200 · Accident: loss of control in flight during landing
From Jefferson County International Airport (0S9) to 1S0 · Puyallup, WA
Event
- NTSB case
- SEA02FA106
- 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
Consolidated Aeronautics Inc. LA-4-200
- Aircraft type
- Consolidated Aeronautics LA-4
- 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
- CGHIT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jefferson County International Airport (0S9), Port Townsend, WATo 1S0 · Puyallup, 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
- 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
Subsequent to the on-scene examination, the accident pilot/aircraft owner contacted the NTSB investigator-in-charge by telephone. During this contact, the accident pilot reported that he was flying the aircraft at the time. He stated that the landing approach was normal up to the runway threshold, but that as the aircraft came over the threshold, it ballooned about 10 to 15 feet into the air, and veered to the left toward parked aircraft and hangars. The pilot said he then added power to go around, but that the airplane's stall warning horn came on and the aircraft subsequently collided with the trees. The pilot reported that there were no mechanical malfunctions or failures with the controls or the engine during the accident.
Probable cause
Failure to maintain aircraft control during a go-around. Trees were a factor in the accident.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA02FA106
- Event ID
- 20020626X00977
- Case number
- SEA02FA106
- 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: 2446ff5d6740c62218056370726489b9d6855bdffe11fb84a91c1965b4bee0bf; retrieved 2026-09-21T09:38:16.619Z.