LAX01LA041 · Experimental Glasair 1RG GLASAIR 1R
Experimental Glasair 1RG GLASAIR 1R · Accident: in flight collision with terrain/water while maneuvering
From Chino Airport (CNO) to Temecula, CA
Event
- NTSB case
- LAX01LA041
- 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
- 2 · 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
Experimental Glasair 1RG GLASAIR 1R
- Aircraft type
- Experimental GLASAIR 1
- 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
- N41AL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chino Airport (CNO), Chino, CATo Temecula, CA
- 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
- Maneuvering
- 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 collision with terrain/water
- 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 › Altitude/clearance, 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
The amateur-built, experimental single engine airplane collided with terrain while performing what a witness described as a series of aerobatic maneuvers. The witness described the airplane as pulling up, rolling, and then diving until out of sight This same maneuver was performed several times. At the bottom of each dive he heard the engine accelerate and the airplane would begin another climb. During the final maneuver, he did not hear the engine accelerate nor did he see the airplane climb again following the descent. A post-accident examination of the wreckage revealed no evidence of preimpact anomalies to the airframe or engine. The pilot logbooks and airplane builder and maintenance records were not recovered. The private pilot accumulated approximately 288 total flight hours, of which an unknown amount were accumulated in the accident airplane. It is uncertain whether the pilot obtained any aerobatic flight training.
Probable cause
the pilot's failure to maintain an adequate terrain clearance altitude while performing aerobatic maneuvers, which resulted in the in-flight collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA041
- Event ID
- 20001212X22305
- Case number
- LAX01LA041
- 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: 42c5395c32fed84efc199350f00a1aa067a69d38e5e58fcf8b2e346e9209920a; retrieved 2026-09-20T20:47:21.447Z.