LAX99LA209 · Blanco SEA HAWKER
Blanco SEA HAWKER · Accident: loss of control in flight en route
From Hemet Ryan Airport (HMT) to UNK · Park City, UT
Event
- NTSB case
- LAX99LA209
- 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
Blanco SEA HAWKER
- Aircraft type
- Blanco SEA HAWKER
- 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
- N2485
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hemet Ryan Airport (HMT), Hemet, CATo UNK · Park City, UT
- 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
- En route · cruise
- 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
- Destroyed
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The owner/builder/pilot of a homebuilt experimental amphibian departed for a personal cross-country flight. About 32 minutes after departure the airplane was observed by witnesses flying north along a ridgeline in a desert area. The airplane made a sudden tight turn to the left and descended into the ground. A postaccident fire consumed the airframe and all engine accessories. One of four carbon fiber propeller blades was found separated from the propeller hub and free of impact damage. The other three blades were fire damaged. A detailed examination of the engine did not reveal any mechanical failure. A sheriff's helicopter pilot reported 'very turbulent and very rough' air above 100 feet agl. The density altitude was about 6,180 feet msl.
Probable cause
A loss of control in flight for undetermined reasons that resulted in an in flight collision with terrain. A factor was turbulent weather conditions in mountainous/hilly terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX99LA209
- Event ID
- 20001212X19024
- Case number
- LAX99LA209
- 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: 7dfd94dc86d43e6ab0ebc32a971426975a2812dc04f7b4a019b56e5572dda842; retrieved 2026-09-20T22:04:00.770Z.