LAX90DUD02 · Reid LONG EZ
Reid LONG EZ · Accident: in flight encounter with weather on approach
From Santa Monica Municipal Airport (SMO) to Santa Monica Municipal Airport (SMO)
Event
- NTSB case
- LAX90DUD02
- 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
- Instrument Meteorological Cond
Reid LONG EZ
- Aircraft type
- Reid LONG EZ
- 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
- N100PY
- Operator
- Reid, William W. · private individual
- Onboard fatalities
- Unknown
- Route
- From Santa Monica Municipal Airport (SMO), Santa Monica, CATo Santa Monica Municipal Airport (SMO)
- 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
- Approach · VFR go-around
- 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
- In flight encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › Aircraft control, not maintained
- Pilot in command › Spatial disorientation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AT THE CONCLUSION OF A LOCAL FLIGHT, THE PILOT ENTERED DOWNWIND FOR LANDING. THE TOWER CLEARED THE AIRCRAFT FOR LANDING AND THE PILOT STATED HE WOULD BE MAKING A 'LONG DOWNWIND.' TWO MINUTES LATER, THE PILOT TOLD THE TOWER THAT HE HAD LOST VISUAL CONTACT WITH THE RUNWAY AND WOULD BE MAKING A GO-AROUND. THREE MINUTES LATER, THE TOWER CONTROLLER QUERIED THE FLIGHT ABOUT ITS POSTION AND THE PILOT RESPONDED THAT 'ACTUALLY I CAN'T TELL.' THAT WAS THE LAST COMMUNICATION WITH THE FLIGHT. THE WRECKAGE WAS FOUND FLOATING ABOUT 4 MILES OFF SHORE. A HELICOPTER PILOT FLYING IN THE VICINITY REPORTED THAT A DENSE FOG BANK WAS MOVING ON SHORE AT THE TIME WITH TOPS AT ABOUT 900 FEET AND BASES AT ABOUT 400 FEET. THE WITNESS SAID THE INFLIGHT VISIBILITY WAS ONE HALF TO THREE QUARTERS OF A MILE BENEATH THE FOG BANK.
Probable cause
THE PILOT'S INFLIGHT LOSS OF CONTROL DUE TO SPATIAL DISORIENTATION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90DUD02
- Event ID
- 20001212X22574
- Case number
- LAX90DUD02
- 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: b33a193725176297cf34154e6add40f3da7c7c16849cbdb5a8246fd4f12197c6; retrieved 2026-09-21T02:56:15.432Z.