elihoole/asrs-aviation-reports huggingface dataset:
Date: 201307
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic System Pump
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Near the top of climb the EICAS message HYD ENG PUMP L appeared along with the associated low pressure light in the pump switch. We referenced the QRH which instructed us to place the switch in the off position. At this time we notified Maintenance Control via ACARS and sent the associated maintenance code. About an hour later we observed the left hydraulic quantity decreasing at a fairly rapid rate. We again referenced the QRH; this time for the HYD QTY-L and were directed to turn off the associated pumps; in this case it was the remaining electric pump. We again contacted Maintenance and during our conversation we observed the left hydraulic quantity decrease to zero. We discussed this with Maintenance and Dispatch and decided to continue to our destination. We asked Dispatch to have CFR stand by [at our destination]; briefed the flight attendants and informed them that we anticipated a normal landing although nose wheel steering might not be available after landing. Upon arrival we configured early for landing and were required to use alternate flap extension and alternate gear extension and then landed without incident. We cleared the runway; had the aircraft inspected and were then towed to the gate. Maintenance determined that the Left Engine Driven Hydraulic Pump had failed and had caused the fluid to leak out of the system.




Synopsis: After their left main engine driven hydraulic pump failed; draining the fluid and causing the electrical standby pump to be unusable; a B757-200 flight crew completed the associated checklists; declared an emergency and; utilizing alternate systems to extend the gear and flaps; landed successfully at their destination where they were towed to the gate.
Date: 201201
Location: ZZZ.Airport, US
Weather elements / visibility: Rain
Light: Night
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Distraction; Communication Breakdown; Time Pressure; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: During the deplaning; I stepped in the forward bulkhead (aircraft right) to step out of the way of the provisioner and agent as they conducted their jobs of provisioning and paperwork exchange with the pilots. It was raining fairly hard as well; and water was blowing in the forward galley door. I was saying goodbye to the passengers. Toward the end of deplaning; a woman who looked to be in her twenties; turned right to exit the aircraft instead of following those people directly in front of her who had turned left and exited properly. I immediately caught her turning and began to say repeatedly; 'NO; NO; NO; NO!!! Ma'am please turn around and go the other way'. The passenger continued on and stepped out onto the provisioning truck; finally stopping; turning around; getting back on the aircraft; and exiting aircraft left. The passenger never said anything to me or any (company) personnel. I should have been in the galley. It is very difficult when at times there are 3 crew members; provisioning and agents all jockeying for the same galley space. Perhaps there is some sort of temporary boundary that could be placed between the galley area and aisle to help passengers avoid mistakes. Although; I'm sure this would be considered a safety hazard.




Synopsis: While deplaning; a passenger turned right into a B737 galley and; with the Flight Attendant calling to her; out into a provisioning truck before realizing the error; turning around and exiting the main cabin door.
Date: 201902
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Electrical Wiring & Connectors
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb Purser called flight deck reporting that FAs (Flight Attendants) in aft galley were experiencing strong electrical burning smell and had the halon extinguisher out and wanted to return to field. FA came back on inter phone and said the smell was very strong and wanted to land. No smoke; fire; or other indications of fire were observed. FO (First Officer) was pilot flying. We coordinated with ATC for level off and the return to ZZZ. Notified dispatch via ACARS of problem; intent to return. Began Smoke; Fumes; Odor checklist.Purser called from aft galley to report that the smell had rapidly dissipated. This was before the checklist portion that isolates electric and air conditioning. Checklist completed. Continued to coordinate with ATC for return. Verified overweight landing. Requested rwy XXR; longest runway. Set up FMC and radios for iOS XXR. Performed descent checklist. Landing uneventful. Taxi to gate uneventful. Made log entry for overweight landing. MX met flight at gate. MX had made the decision to keep pax on plane; and instructed customer service to do so. I asked station to deplane passengers. Called dispatch to report our status. Called [Operations] for briefing/ debriefing. MX discovered that an FA in the aft jumpseat had a phone charger plugged into an outlet by door 2R. MX reported that the lower receptacle was hotter than the upper; the one the FA was using; and that it showed signs of arcing. MX began taking parts off of the jet for another plane that was having difficulties. We elected not to stay with the flight as the departure time was uncertain.


Second narrative: On departure at 12;000 feet the FAs (Flight Attendants) called with fire extinguisher and PBE in hand. Strong electrical smell in aft galley area. They demanded immediate return to airport. I was pilot flying so I just understood the gist of it. I leveled off and slowed down the aircraft. We declared emergency and ran checklist and returned to ZZZ without further incident. We landed overweight.


Synopsis: B737-800 flight crew reported an electrical burning smell from the cabin and returned to departure airport.
Date: 201207
Local time of day: 0601-1200
Location: TTD.Airport, OR
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna Aircraft Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class D TTD
ATC / advisory: Tower TTD
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument
Human factors: Other / Unknown
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On initial climb to the 1;200 FT ceiling below PDX Class B airspace at 1;100 FT MSL; heading 200; I was passed just off my right wingtip by a metallic blue green object. [It was] the shape of a wing; about 2 to 3 FT across; flying parallel to my course at the same altitude in the opposite direction heading toward the 7 approach end of TTD Runway (7/25). I contacted the Tower but they had nothing on radar. I looked back and confirmed that it was blue-green; metallic; and probably 2 to 3 FT; flying on a straight and level path. I quickly lost sight of it. It was not a drifting balloon; it was moving fast and level; probably a remote controlled model aircraft of some sort. The separation from my wingtip appeared to be 10 FT or less.

Callback: Reporter states that she believes the aircraft was a radio controlled model and was essentially identical to one that was found on line; including the color.



Synopsis: Cessna pilot reports a NMAC with a model aircraft at 1;100 FT MSL beneath the PDX Class B Airspace.
Date: 201311
Local time of day: 1801-2400
Location: LFT.Airport, LA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C LFT
ATC / advisory: TRACON LFT
Aircraft component: MCP
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Human-Machine Interface
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control; Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Aircraft Automation Overrode Flight Crew; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: While in descent to an unfamiliar report; though the weather was VMC; I set up and prepared for an ILS approach to back up the visual Runway 4R in LFT. Then new weather came out and I was advised that Runway 11 was now the arrival runway. Though the VOR approach to [Runway] 11 was not available at night; I referenced the altitudes on the approach for descent guidance to the airport after I was cleared for the visual approach. In the meantime I set up the EFIS for a visual approach to the runway. In doing so; I mistakenly set my selected altitude to 0 instead of 'OFF.' In doing so; the flight director commanded a greater descent; which [I] mistakenly followed. By the time I realized my mistake; I received a 'Low altitude warning' from ATC at 850 FT. I climbed back up to 1;000 FT AGL; and made a normal descent and landing. I guess what I take away from the incident was that though the electronic navigation systems onboard the airplane; can be invaluable tools for situational awareness; I still need to use common sense airmanship to help guard against the human errors that still occur.




Synopsis: Single engine turboprop pilot reports setting up the EFIS for a visual approach and mistakenly setting selected altitude to 0 instead of 'OFF.' This results in an early descent and a low altitude warning from ATC.
Date: 201501
Local time of day: 1201-1800
Location: LGA.Airport, NY
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B LGA
ATC / advisory: Tower LGA
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: WE WERE ON 5 MILE FINAL TO LAND WHEN I NOTICED A GREEN LASER POINTING INTO THE SKY AND SWEEPING IN OUR DIRECTION. I WARNED FIRST OFFICER TO AVOID LOOKING IN THAT DIRECTION. THE LASER SWEPT ACROSS OUR AIRCRAFT TWICE THEN TURNED OFF. I REPORTED THE INCIDENT TO ATC; WE CONTINUED TO AN UNEVENTFUL LANDING.


Second narrative: During final approach to runway 4 at LGA; at approximately 1;400 feet AGL; Captain advised me of laser illumination. I observed a very bright light at my 2-3 o'clock position that lasted a few seconds. A few seconds later; a second illumination occurred; lasting approximately 4-5 seconds. I was Pilot Flying and was hand flying the aircraft. I lowered myself in my seat and avoided looking in the direction of the laser. I proceeded to conduct normal landing.


Synopsis: B737 flight crew reports being illuminated by a green laser light at 1;400 feet during approach to Runway 4 at LGA. The reporters are not harmed and a normal landing ensues.
Date: 202002
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Recently on a flight in an Aircraft X; we experienced an Engine Failure which led to a divert. The trip started out like any other day; my First Officer and I had flown together twice before and after pleasantries we got to work. The offer for him to start off flying first was accepted and we blasted off on time. Once we coasted out it was smooth at 32;000 feet so the seat belt sign was off and we were engaged in idle chit chat. I was about to select something on my iPad when we felt a quick yaw/roll to the right. Immediately I heard 'Engine Failure' which I responded 'Your Aircraft.' Pilot Flying started his Non memory memory items and I notified ATC. I requested a lower altitude and got us pointed back towards land. We were approximately X NM off the coast. I did a quick glance to ensure we were well within the drift down profile and then pulled the card. By now the initial shock was over and it was as if we were in the sim doing sim stuff. Once the ECAM was done and QRH follow-up items were accomplished; I gave a quick Flight Attendant update and PA. I re-evaluated our divert airports and shared my thinking with my First Officer. Together we came to a consensus to go to an airport that was 75 miles quicker to get over land. Not only land; but [airport] with too really big long runways. ACARS was sent to Dispatch and I talked to the Number 1 Flight Attendant in more detail. The rest of flight was more or less routine with the stop on runway after landing for proper inspection. It was about an hour between Engine Failure and touchdown.




Synopsis: An Air Carrier reported an engine failure over water and diverted.
Date: 201812
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Check Pilot; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: Descending through FL 180 Center gave us the altimeter setting to ZZZ. We continued our descent to 3000 and got a landing gear warning and ATC said they had a low altitude alert for us. We disconnected the autopilot and climbed; checked the altimeter settings and corrected them then leveled off at 3000. Cause: We were told; heard; or read back the wrong altimeter setting and never checked it to the ATIS to make sure it was correct. Suggestions: Never assume that the altimeter setting you get is correct always double check it to the ATIS.


Second narrative: Center gave instructions to descend to 11000 FT altimeter 30.40. Before reaching 11000 we were cleared to 3000. Upon reaching 3400-3300 landing gear aural message announced and the RA (radar altimeter) indicated 2500. The Captain took off autopilot and climbed till all messages extinguished. I requested another altimeter setting which was 29.40. After setting the new meter we leveled off at the correct altitude and continued the flight with no further complications. Cause: Both pilots in the aircraft heard the 30.40 indication. Either this was inaccurate or both pilots failed to hear the correct information. Suggestions: Be more attentive to local altimeter setting and double check with ATIS and confirm the correct data is imputed and not solely rely on one source of information.


Synopsis: EMB flight crew reported a communication breakdown between flight crew and ATC led to a low altitude situation.
Date: 202104
Location: DEN.Airport, CO
Flight conditions: VMC
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B DEN
ATC / advisory: Tower DEN
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were told to expect the RNP approach to 34L from our initial check in. On downwind we were told to expect the visual instead. We had many speed changes. The final speed change was to expedite our slow down to 170. The First Officer called for gear and flaps as necessary. It didn't look like he was going to level at the final approach fix altitude so I was watching that and the plane in front of us. He never called for the landing checklist and I never thought to do it. I completely lost situational awareness. The First Officer ended up getting a sink rate that was quickly corrected. The plane in front of us gave us moderate wake turbulence. We debriefed and decided this was a failure on both of us to maintain situational awareness.




Synopsis: B737NG Captain reported they failed to complete the landing checklist because of distractions and loss of situational awareness.
Date: 201809
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear Tire
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Aircraft taxied down taxiway after having a rejected takeoff event. Both right main tires burst while taxiing causing heavy damage to gear door and several wing panels. My concern is that the tires bust before the fuse plugs were able relieve the pressure in the tire; putting all those around and in the aircraft in danger.




Synopsis: Maintenance Technician reported B737 blew both right main landing gear tires during taxi after an RTO.
Date: 202001
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: Marginal
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew; Person Passenger
When detected: Taxi; In-flight
Contributing factors: Aircraft; Weather
Primary problem: Weather

Narrative: [While] deadheading in the back of a company airline flight the flight took off with significant wing ice contamination. There was wing contamination and that it continued to adhere to the wing from chassis; takeoff; climb; and cruise phases of flight.




Synopsis: An Air Carrier pilot deadheading in the passenger seating reported the flight departed with icing contamination.