Jaax Flying Service Mitsubishi MU-2B-26A accident
Mitsubishi MU-2B-26A · Accident: wheels up landing
From Banning Municipal Airport (BNG) to Blythe Airport (BLH)
Event
- NTSB case
- LAX05LA178
- 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
- Unknown
- 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
- Charter & commuter
- 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
Mitsubishi MU-2B-26A
- Aircraft type
- Mitsubishi MU-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
- N333WF
- Operator
- Jaax Flying Service
- Onboard fatalities
- Unknown
- Route
- From Banning Municipal Airport (BNG), Banning, CATo Blythe Airport (BLH), Blythe, 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 135: Air Taxi & Commuter
- 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
- Landing
- 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
- Wheels up landing
- 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 › Gear extension, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot failed to lower the landing gear prior to touching down on the runway. The pilot said that during the approach into the airport, the flaps would not lock into the 20-degree extended position. The pilot decided to execute a no-flap landing and referred to the emergency checklist. The checklist advised the pilot to extend the landing gear; however, the pilot skimmed over the information thinking that the gear was already down and locked, and focused on the stabilized approach into the airport. The airplane touched down with the gear in the retracted position. No mechanical malfunctions were noted with the landing gear system on the airplane and a ground test run of the flaps did not reproduce the failure encountered during flight.
Probable cause
the pilot's failure to lower the landing gear prior to landing. A factor to the accident was the pilot's diverted attention due to the flap system anomaly.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05LA178
- Event ID
- 20050525X00670
- Case number
- LAX05LA178
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-03-12.
- API snapshot SHA-256: 8db2bc557cbbf6afbd5e266fa70b0467628f6c04782f493860c916ab1e4ac5fb; retrieved 2026-09-18T15:04:29.021Z.