Boeing 727-223
NTSB investigations · 28
Matched to the registry by N-number and event date, newest first.
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('1384074')
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" 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 c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('1384074')
ORDER BY c."eventDate" DESC, c."ntsbNumber" 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.
NTSB DCA98MA023Accident · Minor injuriesClass 1 · MajorFinal reportBoeing 727-223 · Chicago, ILthe failure of the flight crew to maintain a proper pitch attitude for a successful landing or go-around. Contributing to the accident were the divergent pitch oscillations of the airplane, which occurred during the final approach and were the result of an…NTSB IAD98LA021Accident · Serious injuriesLimited investigationFinal reportBoeing 727-223 · Philadelphia, PAfailure of the tug driver to see-and-avoid the taxiing airplane.NTSB ATL91IA094Incident · No injuriesIncident investigationFinal reportBoeing 727-223 · Nashville, TNThe captain's failure to maintain a proper glide path after disconnection of the autopilot during the final approach. Factors in this accident were: the captain's failure to follow company procedures for category ii approaches, the first officer's failure to…NTSB CHI91IA144Incident · No injuriesIncident investigationFinal reportBoeing 727-223 · Chicago, ILThe failure of the ground crew to properly align the airplane in the gate alley during the push back from the gate.NTSB CHI91IA058Incident · Minor injuriesIncident investigationFinal reportBoeing B727-223 · Des Moines, IAAn oil leak originating from the auxiliary power unit which created smoke in the passenger cabin after it passed through the air conditioning/heating system equipment and associated duct work.NTSB MIA90LA155Accident · Serious injuriesLimited investigationFinal reportBoeing 727-223 · Fort Myers, FLUnforecasted encounter with weather. The airplane encountered severe turblence during enroute descent, resulting in one flight attendant sustaining serious injury, and one passenger sustaining minor injury.NTSB MIA88LA075Accident · No injuriesLimited investigationFinal reportBoeing 727-223 · San Juan, PRN705AA was number two in position for takeoff behind N893AA. N705AA received takeoff clearance first and as it began to taxi to the runway it's left wing tip struck and passed under the right wing tip of N893AA.NTSB MIA87IA237Incident · Minor injuriesIncident investigationFinal reportBoeing 727-223 · Tampa, FLDuring descent the B727 crew noted the fire warning light illuminate on the #1 engine. They discharged 2 fire bottles into the engine but the warning light remained illuminated. They declared an emergency and landed at their destination. An emergency…NTSB MIA87IA068Incident · No injuriesIncident investigationFinal reportBoeing 727-223 · Tampa, FLThe regularly scheduled air carrier flight was climbing to altitude when the engine oil pressure and quantity dropped to zero on the #3 engine; it was shut down. Shortly thereafter, the #1 engine oil pressure dropped to zero. It was reduced to idle and the…NTSB CHI86MA142Incident · No injuriesMajor investigationFinal reportBoeing 727-223 · Chicago, ILU.S. Air flight 373 passed over American airlines flight 695 at the intersection of runways 32R and 4L while both aircraft were taking off. Both aircraft had been cleared for takeoff by the local controller at o'hare tower. The aircraft came within twenty…NTSB ATL86LA090Accident · Serious injuriesLimited investigationFinal reportBoeing 727-223 · Memphis, TNAmerican airlines flight 502 experienced a fire warning light illumination on no. 1 engine as the aircraft was climbing through 6000 feet. The pilot declared an emergency and returned to Memphis. Following the landing the pilot ordered a passenger emergency…NTSB DCA86IA017Incident · No injuriesIncident investigationFinal reportBoeing 727-223 · Harlingen, TXWhile en route, the company dispatcher notified American flt 844 (via acars) that Harlingen (hrl) had unforecast fog & was 300' obscd with 1/2 mi vis. At 2335, as the flt bgn a dscnt fm FL 310, the same ceiling & vis were rprtd. However, as the flt was clrd…NTSB CHI85FA174Accident · Serious injuriesField investigationFinal reportBoeing 727-223 · Little Rock, ARThe aircraft was paralleling a line of thunderstorms and needed to get on the other side of the line to get to his destination. The center controller suggested that he reverse course to fly around the closer end of the line but the pilot decided to penetrate…NTSB SEA84IA037Incident · No injuriesIncident investigationFinal reportBoeing 727-223 · Seattle, WAThe capt stated that upon visual contact with the rwy, the acft was displaced slightly to the lt & he corrected toward centerline with rt rudder. Wing tip contact was neither heard not felt in the cockpit. There were several concurrent reports of arriving…NTSB CHI84IA041Incident · No injuriesIncident investigationFinal reportBoeing 727-200 · Chicago, ILDuring taxi from landing the left outboard wheel rim failed and bounced onto a highway causing damage to a vehicle the rim failed due to a per-existing fatigue crack.NTSB FTW83IA086Incident · No injuriesIncident investigationFinal reportBoeing 727-223 · Memphis, TNDuring a go-around from an ILS approach, the left wing tip was dragged. This resulted in minor damage to the leading edge slats, trailing edge flaps and outboard flap track housing on the left wing. An uneventful landing was made after the go-around. The…NTSB FTW83IA044Incident · No injuriesIncident investigationFinal reportBoeing 727-223 · Little Rock, ARThe aircrew reported that they broke out of the clouds at about 744 ft AGL while on an ILS approach and that the ceiling was ragged. At about 500 ft AGL, the captain turned on the windshield wipers. The first officer was flying the aircraft from thr right…NTSB FTW82DA010Accident · Serious injuriesClosedBoeing 727 · Dal Ftw Arpt, TXNTSB NYC79DA041Accident · No injuriesClosedBoeing 727 · Philadelphia, PANTSB IAD77DA028Accident · Serious injuriesClosedBoeing 727 · Dayton, OHNTSB IAD76AI091Accident · Serious injuriesClosedBoeing 727 · Bethlehem, PANTSB NYC76IN096Incident · No injuriesClosedBoeing 727 · Binghamton, NYNTSB NYC76AN026Accident · No injuriesClosedBoeing 727 · Buffalo, NYNTSB CHI75AC005Accident · Serious injuriesClosedBoeing 727 · Chicago, ILNTSB CHI71AC068Accident · Serious injuriesClosedBoeing 727 · Cincinnati, OHNTSB CHI71IC022Incident · No injuriesClosedBoeing 727 · Kankakee, ILNTSB NYC70AN109Accident · Serious injuriesClosedBoeing 727 · Phillipsburg, PANTSB CHI68A0110Accident · Serious injuriesClosedBoeing 727 · Columbus, OH
Back to Boeing 727-223