Boeing 737-301
FAA incident reports · 38
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 ('138447R')
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 ('138447R')
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 20110330030419ABoeing 737-301 · Laredo, TXOn March 30, 2011, about 2330 zulu, a Boeing 737-300 airplane, N360WA, sustained substantial structural damage during takeoff and climb out from the james cox dayton international airport. The airplane was being operated as flight 360WA, by northern air cargo…Incident 20080419837739IBoeing 737301 · Windsor Locks, CT(-23) Us airways landed runway 6 and was instructed to taxi via runway 19, taxiway tango, cross runway 33 to the ramp. The last time the crew had been at Bradley runway 19 intercept tramway 33 and from that point the ramp could be accessed. Construction…Incident 20021013032329IBoeing 737301 · Greensboro, NC(-23) On very short final, just after flare the aircraft struck a flock of geese. The aircraft landed safely and taxied to the gate. Crew walk around found evidence of bird ingestion in both engines. Us airways maintenance confirmed damage to both engines by…Incident 20020930025319IBoeing 737301 · Texico, TX(-23) On 09/30/2002, 17:25 CDT delta flight 1628, a Boeing B737 was enroute from dfw to ontario, CA. Flight was over Texico, new Mexico at time of incident. White smoke was observed coming from the forward galley area. Flames were not observed, but front of…Incident 20020617019159IBoeing 737301 · Syracuse, NY(-23) On Monday, June 17, 2002, after takeoff from runway 28 at Syracuse Hancock International Airport, the nose gear would not retract on N585US, a Boeing 737-300 operated by usairways. The aircraft returned to the airport and landed without incident. The…Incident 20020323009979IBoeing 737301 · Kansas City, MO(-23) On March 23, 2002 us airways flight 386 a B737 aborted takeoff due to an APU caution light. Aircraft returned to the terminal. Log entry indicated at takeoff roll the APU det. In-op light illuminated, takeoff rejected. The APU fire detection system was…Incident 20011008028439IBoeing 737301 · Buffalo, NY(-23) On Monday, October 8, 2001, N354US, a B-737-301 operated by usairways, inc., after takeoff and during flap retraction, the flaps split and an assemetry trip resulted. The aircraft returned to Buffalo niagara international airport and landed…Incident 20010531015299IBoeing 737301 · Tampa, FL(-23) On may 31, 2001 a B-737-301, N585US operated by us airways airlines, on departure from Tampa International Airport, Florida, (tpa) report "a" hydraulic system failure and returned to tpa and landed without incident. Subsequent investigation revealed a…Accident 20010528011649ABoeing 737301 · Toccoa, GA(-23)This is preliminary information and will be amended when final NTSB report is completed. On mzy 28 2001, at about 0940 EDT, a Boeing 737-301, N349US, flight 351, registered to first union national bank trustee and operated by us airways inc, as a 14 CFR…Incident 20010210002709IBoeing 737301 · Buffalo, NY(-23) On Saturday, February 10, 2001 at 2009 EST, a usairways B-737, N585US, flight 638, landed on runway 23 at the Buffalo niagra international airport after reporting a leading edge flap problem. The reported discrepancy was "le flap transit light remained…Incident 20000627032639IBoeing 737301 · Middletown, PA(-23)Us air flight 1924 was enroute from rochester (roc) to Washington (dca) on an IFR flight when it diverted to Harrisburg, Pennsylvania (MDT) due to an electrical burning smell in the cabin near row #1. No smoke was noted. An after landing post flight…Incident 19990526017339IBoeing 737301 · Albany, NYAircraft departed runway 19. Approximately 45 miles from Albany airport, captain experienced smoke in the cockpit, aircraft returned to land on runway 19 and taxied to the gate withouth further incident. Discrepancy was entered into the aircrfaft logbook.…Incident 19990315017849IBoeing 737301 · Kansas City, MO(-5) On 3-15-1999 at approximately 0710, southwest airlines flight 212 a Boeing 737-300, aborted its take-off. This was due to a throttle split and number 1 engine N1 indicating in the red zone. Southwest airlines contacted contract aviation maintenance (cam)…Incident 19980714036349IBoeing 737301 · Pittsburgh, PAAircraft landed long on runway 32, ran off the end.Incident 19980624040219IBoeing 737301 · South Bend, IN(-5)During climbout the right engine overheat annunciation light came on. Flight crew shut down the engine i/a/w the aircraft checklist and landed back at South Bend, Indiana (sbn) without further incident. Post landing investigation revealed that the low…Incident 19980223005109IBoeing 737301 · Salt Lake City, UTNarrative: [privacy data omitted] when the box was removed by the maintenance personnel it showed signs of smoke (streaking) and had a strong smell of electrical fire. P/N915F212-5, s/n PF4106. Aircraft was approx. 37,000 ft, 80 miles west of slc when the…Incident 19970502033709IBoeing 737301 · Little Rock, ARNarrative: two passengers and a flight attendant received minor injuries after being thrown about the cabin when momentary severe turbulence was encountered near Little Rock, Arkansas at FL350. The seat belt sign was illuminated and a notification call was…Incident 19970322012739IBoeing 737300 · Indianapolis, INNarrative: crew diverted into Indianapolis from planned flight neward to Colorado springs for unsafe gear indication. Contract maintenance from usair did inspection and conferred with W8PA maintenance control, who directed a ferry flight to Colorado springs…Incident 19961025040239IBoeing 737300 · Worthington, PANarrative: the pilot stated he leveled off at FL 260 enroute from philadelphia, due to reports of severe turbulence at FL310 and light chop at FL280. After initially receiving a good ride at FL280, moderate turbulence was encountered. A descent to FL240 was…Incident 19950717023039IBoeing 737300 · Buffalo, NYOn takeoff right engine injested a bird. Returned safely. Fan blades damaged. Replaced.Incident 19950122003829IBoeing 737301 · Indianapolis, INNarrative: aircraft departed pit and experienced #1 generator problem. The APU was transferred to the #1 bus and it dropped off the line also. The captain declared an emergency and landed without incident at ind. Maintenance discovered a bent pin in the #1…Incident 19930520018339IBoeing 737301 · Washington, DCFumes in cockpit. Went on oxygen. Landed safely. Found excessive amount of lps lubricant on pilots seat rails.Incident 19921130050599IBoeing 737301 · San Francisco, CAAfter takeoff pilot was unable to pressurize cabin. Returned. Found out flow valve stuck open.Incident 19921012046589IBoeing 737301 · Pittsburgh, PASmoke and flames from right engine on takeoff. Aborted. Appears to have stage one or two blade failure.Incident 19920223015669IBoeing 737301 · Los Angeles, CACleared and landed on runway 24R. Another aircraft made a go around as it also assigned 24R sidestep to 24L.Incident 19910911044709IBoeing 737301 · Boston, MAOn taxi for takeoff pilot braked aircraft and attendant fell and hurt back.Incident 19910712033389IBoeing 737301 · Kansas City, MOEngine flameout at cruise altitude. Diverted . Relit NR1 engine at FL260. Landed without incident.Incident 19910529024209IBoeing 737301 · Kansas City, MOCaptains instruments going off and on in cruise. Diverted for landing. NR1 generator feeder wire was burned.Incident 19901027061359IBoeing 737301 · Rochester, NYAborted takeoff two times due to high EGT indication on left engine. Replaced the EGT harness.Incident 19900721063929IBoeing 737301 · Newark, NJPassenger became abusive and unruly on approach. Refused to sit down. Arrested at gate.Incident 19900311013479IBoeing 737301 · Baltimore, MDElectrical failure due to relay failure. On landing air cycle machine overheated and smoked. Evacuated aircraft.Incident 19900310003649IBoeing 737301 · Baltimore, MDPartial electrical failure en route. Relay failure. On landing air cycle machine overheated and smoked. Evacuted.Incident 19891120062579IBoeing 737301 · Philadelphia, PADiverted due to weather. Upon arrival advised to hold. Declared low fuel. Proceeded to alternate airport.Incident 19890826058269IBoeing 737301 · Dayton, OHStabilizer struck jetway while taxiing out of gate area. Marshal giving instructions. Jetway out of position.Incident 19890130023189IBoeing 737301 · San Jose, CAPressurization problems on takeoff. Returned. Found aft cargo door open. Warning light switch in closed positionIncident 19890110008739IBoeing 737301 · West Palm Beach, FLSmoke from cabin and cockpit ducting. Nose wheel APU warning. Passengers evacuated. Suspect oil seal leak.Incident 19881120063339IBoeing 737301 · Las Vegas, NVPassenger locked self in lavatory and became noisy. Emergency landing at Las Vegas. Escorted by police to hospital.Incident 19880821050159IBoeing 737301 · Las Vegas, NVPilot aborted takeoff due to blown tires on right gear. Overhead oxygen panels came loose falling on 6 passengers.
Back to Boeing 737-301