LAX93LA131 · Schicora OSPREY 2
Schicora OSPREY 2 · Accident: in flight collision with terrain/water during initial climb
From L80 to L80
Event
- NTSB case
- LAX93LA131
- 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
Schicora OSPREY 2
- Aircraft type
- Schicora OSPREY 2
- 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
- N186S
- Operator
- William R. Schicora · private individual
- Onboard fatalities
- Unknown
- Route
- From L80To L80
- 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
- Initial climb
- 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
- 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
- Stall/mush
- 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 › Lift-off, premature
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT BUILDER WAS FLYING THE AIRCRAFT FROM THE RIGHT SEAT AND PROVIDING FAMILIARIZATION TRAINING TO A FLIGHT INSTRUCTOR WHO WAS TO TEACH THE NEW AIRCRAFT OWNER HOW TO FLY THE AIRCRAFT. THE PILOTS SAID THAT THE GROUND ROLL AND ROTATION WERE NORMAL AND THE AIRCRAFT LIFTED OFF THE RUNWAY AT ABOUT 60 KNOTS. BOTH PILOTS STATED THAT THE AIRCRAFT WOULD NOT CLIMB ABOVE 10 FEET AGL AND IT SETTLED BACK TO THE GROUND OFF THE RIGHT SIDE OF THE RUNWAY AND COLLIDED WITH SOME BRUSH AND THE TERRAIN. BOTH PILOTS STATED THAT THE WINDS WERE CALM AT THE TIME OF THE ATTEMPTED TAKEOFF AND THERE WAS NO MECHANICAL MALFUNCTION OF EITHER THE AIRCRAFT OR ENGINE. THE AIRCRAFT BUILDER STATED THAT AT THE GROSS WEIGHT AND OUTSIDE TEMPERATURE CONDITIONS EXISTING AT THE TIME THE AIRCRAFT SHOULD HAVE HAD A RATE OF CLIMB OF ABOUT 800 FEET PER MINUTE.
Probable cause
THE FAILURE OF THE PILOT FLYING TO ATTAIN ADEQUATE AIRSPEED FOR LIFT OFF AND THE RESULTING INADVERTENT STALL MUSH CONDITION DURING THE INITIAL CLIMB.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX93LA131
- Event ID
- 20001211X11852
- Case number
- LAX93LA131
- 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: f160627d71590a2c23d6c9df057fa5f94825ebd90935e18fee117d8a0dac3f44; retrieved 2026-09-21T23:02:03.353Z.