Mitsubishi MU-2B-36
FAA incident reports · 20
Matched to the registry by N-number and event date, newest first.
Query with SQL
duckdb -csv -c "SELECT report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE aircraft_model_code IN ('5780412')
ORDER BY event_date DESC, report_number DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE aircraft_model_code IN ('5780412')
ORDER BY event_date DESC, report_number DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
Incident 20070112007749IMtsbsi MU2B36 · Chicago, IL(-23) Pilot stated that during the circle to 22L, he selected gear down and was reaching for the flap selector when he heard a large bang and saw a flash outside the right side of the airplane. He looked to find the right propeller feathered. He ran the…Accident 20050922025139AMtsbsi MU2B36 · West Memphis, AR(-23) On September 22, 2005, at 1958 central daylight time, a mitsubishi MU2B-36, N103RC, operated by mcneely charter services, was destroyed when it impacted a 62,000 pound TS-14 earthmoving scrapper and terrain in a flat field approximately three miles…Incident 20050524013439IMtsbsi MU2B36 · Milwaukee, WI(-23) Pilot stated he used 20 degrees flap and an approach speed between 120 and 135 kt and overshot the touch down spot while landing rwy 7L. The tire skid marks from braking began at the intersection of rwy 13 and 7L and continued to 100' beyond the end of…Incident 20040827025619IMtsbsi MU2B36 · Chicago, IL(-23) After shutdown and the pilot departing the aircraft the right engine started on fire. The fire department was called and the fire extinguished.Accident 20040325003729AMtsbsi MU2B36 · Pittsfield, MA(-23) On March 25, 2004, at approximately 0535 EST, N201UV, royal air cargo flight number 747, operating as a part 135 air cargo flight, departed level flight at 17,000' for unknown reasons. The aircraft pitched up 400', down 900', up 400' and then began a…Incident 20000714034859IMtsbsi MU2B36 · Savannah, GA(-23) Gear up landing go around normal landing made.Incident 19970807027239IMtsbsi MU2B36 · Rockford, ILNarrative: at rotation speed, on departure from rfd rwy 19, a loud bang was heard and vibration felt. Acft was rotated into air and seemed normal. Assumed tire had failed. Contacted company and deviated to yip. Did fly-by for ground visual on gear and made…Accident 19960720019079AMtsbsi MU2B36 · Scottsdale, AZRight engine blew on climbout. Landed on street. Hit rock wall. Turbine rotor disk failed.Incident 19960229007699IMtsbsi MU2B36 · Pontiac, MINarrative: aircraft was inbound into Oakland-Pontiac Airport (ptk). At 0008 local, the pilot reported rapid depressurization and that he lost a window in the back of the aircraft. The aircraft landed at ptk, runway 9R at 0021 local without further incident.…Incident 19951212045669IMtsbsi MU2B36 · Tulsa, OKNarrative: aircraft departed on 135 cargo only flight when at 6 to 7,000 feet, the pilot door blew off. Pilot declared emergency, returned to airport, and landed without incident. No injuries. Door had separated at hinge. No other damage. M or d to follow.…Incident 19920921040859IMtsbsi MU2B35 · Albuquerque, NMRight engine failed on takeoff roll. Aborted. Secured engine. Returned to ramp.Incident 19910929047519IMtsbsi MU2B36 · Morgantown, WVLoss of power on left engine en route. Shut engine down. Landed at destination safely.Accident 19900906038359AMtsbsi MU2B36 · Nashville, TNSlow takeoff. Hot day. Stalled, crashed and burned. No engine defects found.Incident 19900126004169IMtsbsi MU2B36 · Parkersburg, WVLeft engine fire warning. Shut engine down. Landed safely. Cause was a false fire warning signal.Incident 19890713041249IMtsbsi MU2B36 · Springfield, MOLeft cockpit side window blew out en route. Forced landing. Window had been altered when escape door installed.Incident 19871214076489IMtsbsi MU2B36 · Mcalester, OKWindshear on three VOR approaches. Touchdown with gear up on second with go around and normal landing on third.Accident 19840609023479AMtsbsi MU2B36A · Sugarland, TXDamaged occurred when pilot allowed the aircraft to land short of the runway.Incident 19830204030709IMtsbsi MU2B36 · Salina, KSLanded in 18 inch deep snow on a portion of closed runway. Collapsed nose gear. Given NOTAM at weather briefing.Incident 19801211088949IMtsbsi MU2* · Midland, TXPilot moved gear selector switch to down position but failed to visually check position.Incident 19790523027679IMtsbsi MU2B36 · Abilene, TXLanded with engine shut down, ran off end of runway. Found failed gear shaft.
Back to Mitsubishi MU-2B-36