MIA00FA129 · Learjet 35A
Learjet 35A · Accident: in flight collision with object on approach
From Miami-Opa Locka Executive Airport (OPF) to Marianna Municipal Airport (MAI)
Event
- NTSB case
- MIA00FA129
- 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
- 3 · 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
Learjet 35A
- Aircraft type
- Learjet 35
- 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
- N86BE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Miami-Opa Locka Executive Airport (OPF), Opa-locka, FLTo Marianna Municipal Airport (MAI), Marianna, FL
- 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 pattern final
- 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 object
- 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
- Tree(s)
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot canceled the IFR flight plan as the aircraft crossed the VOR and reported the airport in site. The last radio contact with Air Traffic Control was at 0935:16. The crew did not report any problems before or during the accident flight. The distance from the VOR to the airport was 4 nautical miles. Witnesses saw the airplane enter right traffic at a low altitude, for a landing on runway 36, then turn right from base leg to final, less than a 1/2-mile from the approach end of the runway. Witnesses saw the airplane pitch up nose high, and the right wing dropped. The airplane than struck trees west of the runway, struck wires, caught fire, and impacted on a hard surface road. This was a training flight for the left seat pilot to retake a Learjet type rating check ride he had failed on March 24, 2000. He failed the check ride, because while performing an ILS approach in which he was given a simulated engine failure, and he was transitioning from instruments to VFR, he allowed the airspeed to decrease to a point below Vref [landing approach speed]. According to the company's training manual, "...if a crewmember fails to meet any of the qualification requirements because of a lack in flight proficiency, the crewmember must be returned to training status. After additional or re-training, an instructor recommendation is required for reaccomplishing the unsatisfactory qualification requirements." The accident flight was dispatched by the company as a training flight. On the accident flight a company check airman was in the right seat, and the check ride was set up for 0800, April 5,2000. The flight arrived an hour and a half late. The left seat pilot's, and the company's flight records did not indicate any training flights, or any other type of flights, for the pilot from March 24, 2000, the date of the failed check flight, and the accident flight on April 5, 2000. The accident flight was the first flight that the left seat pilot was to receive retraining, and was the only opportunity for him to demonstrate the phase of flight that he was unsuccessful at during the check flight on March 24th. Examination of the airframe and engine did not reveal any discrepancies.
Probable cause
the pilot's failure to maintain control of the airplane while on final approach resulting in the airplane striking trees. Factors in this accident were: improper planning of the approach, and not obtaining the proper alignment with the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA00FA129
- Event ID
- 20001212X20873
- Case number
- MIA00FA129
- 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: d2608660ff434399ace3ef2cecfc58ac9f4570bcc13d4e26c5fed398e4d6fccf; retrieved 2026-09-20T21:21:42.595Z.