elihoole/asrs-aviation-reports huggingface dataset:
Date: 201906
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Distraction; Situational Awareness; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure; Company Policy
Primary problem: Ambiguous

Narrative: As we were pulling in to Gate X; I noticed the fuel cart on the right side was not in the painted yellow dashed liners designated for the fuel pump cart. The Marshallers were holding their wands up still vectoring us in. I advised the Captain to stop and waved to the right side Marshaller to move the fuel cart back in to the lines. They refused to move the cart and waved us in. I showed the Captain and she urged them to move the cart; but they would not; and marshalled us in. The wing and engine was clear of the fuel cart; but I was uncomfortable. After shutdown; I went to speak with the Ground Personnel about the cart placement. The Fuel Technician acknowledged the cart was outside the lines; but said the hose was not long enough to reach the ground fuel port if it was parked within the lines; so they just parked it outside the line towards the aircraft. He also added that 'we are moving to different gates soon so it does not really matter; and the issue will soon be fixed'. I told him we are not allowed to pull in to the spot with the cart out of the lines with the Safety Zone not clear; he reiterated the statement above. I believe this needs to be addressed by moving the cart within the lines or repainting the lines if the current spot of the cart meets clearance requirements.




Synopsis: B737-700 First Officer reported fuel cart not positioned properly during taxi in and ground personal unwilling to correct the situation.
Date: 201812
Local time of day: 0601-1200
Location: IAH.Airport, TX
Light: Dusk
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B IAH
ATC / advisory: Tower IAH
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Deviation / Discrepancy - Procedural Landing Without Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Flying 180 heading to intercept the LOC for [Runway] 26L; we hit some wake turbulence; I think 5 times in all. ATC kept slowing us down and we missed the landing clearance.[I] tried to get the Pilot Flying to stay a little high on the glide path but he just left the autopilot on till 400 feet.




Synopsis: EMB-145XR Captain reported a wake turbulence encounter distracted them and they missed the landing clearance.
Date: 201308
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: B737 Undifferentiated or Other Model
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: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Human factors: Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The flight [was] in cruise at FL370. Clear weather conditions; smooth air. Without warning; we experienced a loud 'bang' accompanied with strong airframe vibration. Number 2 Engine N1 started fluctuating between set power and 50% without moving the thrust lever. This continued as we analyzed the situation; so proceeded to 'Engine Failure' QRH checklist; which led us to shut down the engine. (Later; during the descent; we also reviewed the 'Engine limit or surge or stall' checklist; which led to the same conclusion.) After completing QRH; I gave aircraft control to the First Officer and proceeded to tell ATC that we are declaring an emergency due to engine failure and initiated diversion to an airport now about 15 NM to our north. Then called Dispatch via VHF AIRINC and advised them of the situation and my intentions. Then [I] gave the cabin crew a full briefing on the situation; then a PA to the passengers. Remainder of descent and landing went according to plan and training via the One Engine Inop Approach and Landing procedures. Landing was overweight by 3;300 LBS; but smooth and uneventful. Taxi to parking was normal. Passengers were required to stay on the aircraft for about 40 minutes from that point until airport personnel could arrive with air stairs and open the terminal building; but no complications.




Synopsis: A B737 crew at FL380 in level flight; experienced a loud engine report accompanied by a strong airframe vibration and surging power. They completed the ENGINE FAILURE QRH; declared an emergency and diverted to a nearby airport.
Date: 201704
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Light: Night
Aircraft: B757 Undifferentiated or Other Model
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: Galley Furnishing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After level off at FL370; EICAS LAV SMOKE illuminated; I called AFT galley and the FA confirmed smoke and alarm but did not know source at that point; stated she'd call me back; I told her to turn off the ovens first and investigate. Asked ATC for descent and was given FL240; made a normal descent while considering divert. FA called back and stated ovens were off and she was removing food from ovens and thought that was the source and I stated LAV SMOKE EICAS was not illuminated. Ran QRH and referred to pilot awareness for LAV SMOKE; elected to notify dispatch of our intentions to continue and climb back to FL370 with plenty of fuel above planned flight plan fuel. FA pulled circuit breaker to oven Number 3 in aft galley to ensure no power to it and did not use those ovens for remainder of flight. Did not deviate from ATC clearance but did advise them of our situation without declaring an emergency and then our intentions to continue.


Second narrative: [Report narrative contained no additional information.]


Synopsis: B757 flight crew reported continuing to destination after experiencing smoke from a galley oven.
Date: 201509
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: We received a very late gate change. The ACARS started flashing as we were clearing the active runway. Ground was confused as were we. We had just checked 10 mins prior and were going to C-18. Now Ops wanted us at E-14. We had to verify. Finally we taxied to the south ramp area and had to await outbound aircraft. Once clear we started in; approaching E-14; the guidemen were not in position and there were numerous vehicles/personnel between us and the gate. We stopped. Airport maintenance was painting signs on the tarmac directly in our required path to the gate. We sat. Finally; the lead went over to the mx personnel to move; they did. Then had to get other vehicle including a fuel truck to move to give us clearance to taxi in.After several minutes; two wing walkers arrived and started out to their positions. With them moving; the lead gave me guidance signals to start in. I complied looking mostly ahead and right (fuel truck; ground maintenance truck; numerous personnel were all on the right). All of the sudden a Ford Pickup came into my peripheral view from the left. I hit the brakes quickly not wanting to hit the truck nor rock my passengers. We came within 10 ft of the truck per my estimate; he disappeared under the nose. Ramp Tower was informed but didn't see anything per usual.




Synopsis: A320 Captain reports receiving a gate change after landing then having to wait for outbound traffic before being cleared in. Before reaching the gate; airport personnel painting lines on the ramp along with their vehicles are blocking further progress. Once vehicles and personnel are clear and wing walkers have arrived; the Marshall directs the aircraft into the gate only to have to stop abruptly to avoid a truck dashing through the gap.
Date: 201904
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Ramp
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: [Smart] bag arrived in ZZZ with battery installed.




Synopsis: Ramp employee reported a smart bag was transported with battery installed in violation of Hazmat regulation.
Date: 202010
Location: EGGX.ARTCC, FO
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
ATC / advisory: Center EGGX
Aircraft component: FMS/FMC
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
Human factors: Time Pressure; Human-Machine Interface; Confusion; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was initially the PM (Pilot Monitoring) until approximately XA:50Z.  I was the first pilot to go into crew rest. The RF2 (Relief Pilot 2) and FO (First Officer) received the oceanic clearance at XA:58Z. There were no changes to the routing to the first oceanic waypoint and beyond in accordance with oceanic verification procedures. The following is the write up of the incident that occurred while I was in crew rest:Navigation error from FMS on ETOPS route. Crew verified oceanic routing in accordance with ETOPS procedures. Route was [...]. Crossing PIKIL in LNAV/VNAV; aircraft entered right turn as expected but turned past cleared route. PF selected heading select and returned to planned MAG HDG. Position report page showed passing 59n030w at the time we passed PIKIL with (coordinates X) next and (coordinates Y) after; (next +1). PIKIL was not depicted on the position report page. Coincidentally; PM had just accepted and executed flight level winds. Both FMSs showed same problem around PIKIL.After I came out of crew rest; the PM and PF (Pilot Flying) briefed me about the navigation incident. They had a properly programmed FMS with no modifications to the waypoints. The airplane behaved unexpectedly with a continual turn passing the first waypoint PIKIL and deviating from the magenta course line. They appropriately downgraded from the highest level of automation to correct the error. The RF2; who was the PM; captured the POS REPORT page when time allowed. The operating crew requested updated winds aloft around XC:00Z and were made available and executed around the time of PIKIL. Perhaps the new winds caused the FMS anomaly and shouldn't be requested anywhere near the first ocean entry point. This was stated as a known anomaly with the B767 FMS.




Synopsis: B767 Captain reported an internal aircraft issue which made the aircraft make a continual turn passing the first waypoint and deviating from the magenta course line.
Date: 202105
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 75
Light: Daylight
Aircraft: Luscombe Model 8/Luscombe 50
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class G ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Just after liftoff from a touch and go; the engine failed with a loud squealing noise.  I lowered the nose and easily landed on the remaining runway.  There was no sign of fire; I accomplished the shutdown procedures and got out of the plane.  I visually checked the pattern and did not see any traffic; nor did I hear any on the CTAF the last two times around the pattern.  I pushed the plane about 50 feet to the next taxiway and got it clear of the runway.  What I forgot to do was make any announcements on the CTAF after my engine failed.  If it was busy; I am pretty sure I would have made a call that I had landed again and would be occupying the runway for a few minutes; and then another call to say I was clear.  Even so; I should have made those calls in case there was some traffic I was not aware of.




Synopsis: Luscombe 8E pilot reported an uneventful runway landing due to total engine failure shortly after liftoff.
Date: 201902
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Rejected Takeoff
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Upon runway entry First Officer was the flying pilot. Power was applied and noted that both engines started to spin up together. At that point the First Officer put both levers into the FLX position. As he was making the call for 'Check Thrust'; I noted the aircraft was pulling to the left and requiring more rudder than usual. There were no warning or cautions. I checked the thrust and saw the left engine was producing FLX thrust and the right engine was producing TOGA Power. I checked both thrust levers were in the FLX detent. They were and there was no aural warning to the contrary. I called REJECT and brought the thrust levers to idle due to the First Officer having a hard time maintaining the centerline of the runway. I was going to let the aircraft roll towards the next high speed taxiway. After a lag of approximately 2 seconds the Rejected Takeoff (RTO) MAX brakes kicked in. RTO checklist was call for and aircraft was taxied off the runway.The brakes heated up due to the MAX braking; approximately 325 degrees Maintenance Control was notified. During this time the brakes cooled back into the normal range and we taxied back to the gate. Contract MX performed tests in conjunction with Maintenance Control all of which were normal. We were re-released back to ZZZ and chose to do a TOGA takeoff. Normal takeoff and trust reduction with no problems.




Synopsis: A320 Captain reported a rejected takeoff due to asymmetric engine thrust.
Date: 202001
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-800
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Conflict NMAC; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Passenger
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: During deplaning; a passenger approached me and asked about an aircraft that we got very close to. I responded that I was unaware of any abnormally close aircraft during our flight. He responded that we had gotten about 200 ft. away from what he thought was [another] aircraft. I asked him where he thought this occurred and he said; 'somewhere over ZZZ I think'. I assured him that our minimum separation enroute was 1;000 ft. and that we had no close encounters with any other aircraft. He claimed he knew exactly what 1;000 ft. looked like and that the aircraft he saw was definitely 200 ft. away. I asked him if he knew what kind of aircraft it was; hoping to explain that large aircraft appear closer but he said he had no idea what type of aircraft it was; just that he thought it was a (other carrier) aircraft. I again mentioned that we had not come closer to any other aircraft than the standard separation of 1;000 ft. We had no traffic alerts nor any other TCAS has events for the entire flight. The passenger left the jetway after this short conversation.




Synopsis: B737 Captain reported that a deplaning passenger expressed concern that during cruise another aircraft had passed closeby; with less than 1;000 ft of separation; although the separation standard had been met during flight and that no TCAS events had occurred.
Date: 201201
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: B767-300 and 300 ER
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: Electrical Distribution Busbar
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Troubleshooting; Training / Qualification; Situational Awareness; Communication Breakdown
Second reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: About 1 hour after takeoff; received status message 'CA INST TXFER BUS'. Elected to return to the departure airport. Declared emergency due to overweight landing. Landed without incident at approximately 332;500 LBS gross weight. Swapped into different aircraft and flew to the planned destination.


Second narrative: We were unable to contact Dispatch by any means at this time.


Synopsis: An B767-300 CAPT INST TRANSFER BUS status message alerted while in cruise so an emergency was declared and the flight returned to the departure airport.
Date: 201305
Local time of day: 0001-0600
Location: ZZZZ.Airport, FO
Flight conditions: IMC
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZZ
Aircraft component: Air Data Computer
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [We had a] normal takeoff (mine) with standard power. Acceleration and liftoff was normal. During climb out CADC #2 fails. Emergency declared and ILS approach was executed via vectors. No ATC deviation or procedural deviation occurred and under maximum landing weight. Normal landing and rollout. As these aircraft age; special attention to electrical and pneumatic connections should be emphasized.


Second narrative: First Officer's takeoff; shortly after takeoff; #2 CADC failed. Emergency declared. VFR conditions. Received vectors by Departure back to an ILS approach. Landing [was] uneventful.


Synopsis: MD82 flight crew experiences a CADC failure shortly after takeoff and returns to the departure airport after declaring an emergency.