Boeing 737-247
FAA incident reports · 45
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 ('138448D')
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 ('138448D')
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.
Accident 20050117001589ABoeing 737247 · Covington/Cinci, KY(-23) At approximately 1240EST on 01/17/2005 delta airlines aircraft N373DL, a Boeing 737-247 series boarding passengers for flt 583 sustained substantial damage from a provisionary truck operated by gate gourmet employee [privacy data omitted] the gate…Incident 20000621033199IBoeing 737247 · Kansas City, MO(-23)On June, 21, 2000, vanguard airlines, flight 303, aircraft 912MP was scheduled to enroute from mci to den. On initial climb out, cabin pressure, auto fail, illuminated. The crew switched to standby and received a 1,000 feet per minute climb in the cabin…Incident 20000617021739IBoeing 737247 · Kansas City, MO(-23) On June 17, 2000, at approximately 0726 CDT, delta airlines express flight 2589, a Boeing 737-247, N382DL, departed Kansas City International Airport, Kansas City, MO (mci). During climb, an odor was detected and flight returned to mci. Delta…Incident 20000211002639IBoeing 737247 · Kansas City, MO(-5) On 2-11-2000, delta airlines flight 2585, declared an emergency and returned to Kansas City International due to electrical smoke in the cockpit. The pilot reported on log page 627630, that during climbout, passing flight level 220, smoke flowing from…Incident 19991113037819IBoeing 737247 · Minneapolis, MN(-23) Vanguard airlines flight 703 from mdw to msp on approach to msp declared an emergency due to a flap malfunction. Aircraft landed without further indicent at msp. Investigation determined cable from left flap to flap power unit broke. Flight crew was…Incident 19990918028259IBoeing 737247 · Syracuse, NY(-23) On Saturday, September 18, 1999 at 1647 EDT, a Boeing 737, N377DL, flight 1022, operated by delta airlines, during approach to Syracuse Hancock International Airport experienced an engine #1 low oil pressure light illumination. A landing was…Incident 19990616022749IBoeing 737247 · Kansas City, MOAfter takeoff, nose gear indicator light would not illuminate. Pilot returned to mci and landed without incident. Maintenance found open circuit breaker and shorted light assembly. After replacement of light assembly, the aircraft was returned to service.…Incident 19990415019679IBoeing 737200 · Kansas City, MO(-5) On takeoff from mci, the pilot selected gear up. Both main landing gears retracted, the nose gear did not. The pilot selected gear down. All gears indicated down and locked. Aircraft returned to mci without further incident or injury to passengers or…Incident 19990203012129IBoeing 737247On February 23,1999, vanguard airlines, flight 817, a Boeing 737, was enroute from mci to dfw and turned back to mci due to hydraulic system failure. An emergency was declared and the pilot landed the aircraft at mci without further incident. The captain…Incident 19980324007959IBoeing 737247 · Greensboro, NCNarrative: pilot statement: "on climb out of iad at about 17,000 feet, we felt a violent bump. We asked the center about any aircraft in the area, they had none. Aircraft flew normal, upon landing at gso we informed maintenance that we thought we had hit a…Incident 19980128004679IBoeing 737200 · Middletown, PANarrative: on January 28, 1998 at 14:22 hours (local) a Boeing 737-200, N381DL, registered to delta airlines, took-off from Harrisburg international (MDT) enroute to atlanta, ga (atl). At 2000 feet, the number 2 engine compressor stalled. The…Incident 19970627024059IBoeing 737247 · Dallas-Ft Worth, TXDiverted, due binding horizontal trim. Found trim control wheel bearing failed, caused trim wheel to bind.Incident 19931213048659IBoeing 737247 · Wichita, KSCargo compartment door warning light on. Returned. Found faulty door light switch.Incident 19930510017499IBoeing 737247 · Buffalo, NYVibration in NR1 engine on descent. Throttled back. Landed safely. Changed engine.Incident 19930224005079IBoeing 727247 · Buffalo, NYLoud bang on climb. Shut NR2 engine down. Returned. Landed safely. Dome assembly was replaced.Incident 19920908041209IBoeing 737247 · Columbus, OHWing tip struck the jetway on a power out from the gate. Pilot under direction of aircraft marshaller.Incident 19901203063759IBoeing 737247 · Jackson, MSElectrical odor in cabin. Declared emergency and diverted for landing.Incident 19901124061829IBoeing 737247 · Newark, NJPilot aborted takeoff due to nose wheel steering problem. Did not return to gate or write up in log.Incident 19900624040429IBoeing 737247 · Rapid City, SDCrew smelled odor of burning wire. Pilot made unscheduled landing at Rapid City.Incident 19900215008939IBoeing 737247 · Memphis, TNEncountered severe turbulence en route. A seat bolt sheared where an overweight passenger sat.Incident 19891012053959IBoeing 737247 · Oklahoma City, OKReceived bomb threat. Diverted to Oklahoma City. Emergency evacuation. Two passengers slightly injured. No bomb foundIncident 19891002055929IBoeing 737247 · Covington - Cin, OHHydraulic a system failed en route. Returned. Landed safely. Found a defective line.Incident 19890620038709IBoeing 737247 · Kansas City, MOAircraft yawing after takeoff. Yaw damper became ineffective. Returned. Replaced damper coupler system.Incident 19890529031019IBoeing 737247 · Milwaukee, WIExperienced a flame out in left engine during descent. Landed without incident. Cause not stated.Incident 19890418022749IBoeing 737247 · Detroit, MIRight main landing gear struck a deer which was on the runway. Taxied to gate without further incident.Incident 19890206017099IBoeing 737247 · Jacksonville, FLAircraft may have struck approach lights when it made a takeoff during a touch and go.Incident 19881127067259IBoeing 737247 · Edwards, CADeclared emergency. Destination fogged in. Slat problem,landed Edwards Afb. No slat defect but did have fuel problemIncident 19881030057609IBoeing 737247 · Kansas City, MODuring takeoff, tower notified sparks coming from right engine. Returned. Blade damage to compressor.Incident 19881028059949IBoeing 737247 · Dallas-Ft Worth, TXReceived bird strikes to both wings and copilot's windscreen on takeoff. Returned. Damage to slats and leading edgeIncident 19880518023239IBoeing 737200 · Kansas City, MOLost pressurization on climbout. Cabin oxygen masks deployed. Returned. Found a faulty acm air cycle machine.Incident 19880208013879IBoeing 737247 · Detroit, MIUnauthorized use of placarded APU overnight resulted in fire damage to horizontal stabilizer elevator,fuselage skinIncident 19870610028699IBoeing 737247 · Salt Lake City, UTUnable to maintain cabin pressure. Returned. Pac valve failed, air cycle machine, modulating valve replaced.Incident 19870427040689IBoeing 737247 · Salt Lake City, UTUnable to move gear handle without override. Replaced landing gear accessory box.Incident 19860129012759IBoeing 737247 · Phoenix, AZWhile pulling off to side of taxiway to await IFR clearance, wingtip struck a blast fence. Navigation lens broken.Incident 19860102003299IBoeing 737247 · Salt Lake City, UTReturned when course bars on HSI stuck in full left position. VOR test button stuck. Nav com panel replaced.Incident 19851213071379IBoeing 737247 · Missoula, MTAn IFR departure was made with weather conditions below required minima.Incident 19851107059269IBoeing 737247 · Salt Lake City, UTCould not use NR1 comm, VOR or DME after takeoff. Returned and replaced frequency selector panel, DME interrogator.Incident 19851016055989IBoeing 737247 · Salt Lake City, UTNumber 1 engine shutdown due to loss of throttle control. Safe landing. Rod end bearing broke.Incident 19830119007029IBoeing 737247 · Boise, ID4 Main tires blew out on roll out. Brakes cold. Replaced brakes and anti skid devices.Incident 19801202085779IBoeing 737247 · Denver, COZa flight diverted due to flight control malfunction. Found flap control cable broken.Incident 19800417049289IBoeing 737247 · Las Vegas, NVPilot smelled smoke. Fuel indicator shorted and failed.Incident 19800215021159IBoeing 737247 · Ontario, CAFlight diverted to las vegas due to pressurization problems.Incident 19790817031899IBoeing 737247 · Los Angeles, CADuring takeoff main gear tire cap separated. Tire did not go flat. Damage to other aircraft structures.Incident 19790529028409IBoeing 737* · Pierre, SDPublic complaint about low flying aircraft.Incident 19781003031049IBoeing 737247 · Las Vegas, NVPilot lost directional control during take off. No discrepencies found. Steering had been worked on.
Back to Boeing 737-247