LAX96LA118 · Rockwell 112B
Rockwell 112B · Accident: overrun during takeoff
From Q40 to Montgomery-Gibbs Executive Airport (MYF)
Event
- NTSB case
- LAX96LA118
- 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
Rockwell 112B
- Aircraft type
- Rockwell 112
- 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
- N1233J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Q40To Montgomery-Gibbs Executive Airport (MYF), San Diego, 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
- Takeoff · rejected takeoff
- 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
- Overrun
- 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 › Aborted takeoff, delayed
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he initiated a takeoff with 20 degrees of flaps and rotated at what he felt was the normal speed. As the airplane climbed about 20 feet, the stall warning horn sounded, and the airplane ceased climbing. The pilot believed the airplane would not clear buildings at the departure end of the runway, so he elected to abort the takeoff. The pilot was unable to stop of the remaining runway. Subsequently, the airplane encountered a muddy area, and the nose gear collapsed. The pilot believed that the airplane encountered a wind shear that was induced by buildings near to the runway. Using the estimated temperature and pressure altitude, performance charts in the flight manual showed that a takeoff with 20 degrees of flaps would require 1,600 feet to clear a 50-foot obstacle. The landing distance chart from a 50-foot altitude (with full flaps) showed a minimum required distance of 1,200 feet. The runway was 2,700 feet in length.
Probable cause
the pilot's improper planning/decision and delay in aborting the takeoff. Factors relating to the accident were: the short runway, high obstructions near the departure end of the runway, and wind shear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96LA118
- Event ID
- 20001208X05286
- Case number
- LAX96LA118
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-02-17.
- API snapshot SHA-256: e62a37c815296bdc663faf22d6d1ba2ce033056c89679af8f0c5885de1c1e52b; retrieved 2026-09-22T22:48:54.853Z.