elihoole/asrs-aviation-reports huggingface dataset:
Date: 201509
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC Overrode Automation
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was the Captain and PF. At around 18;000 feet ATC ask[ed] us to climb 2;000 feet per minute through FL260 on our way up to FL350. I then set the VS mode and selected 2;000 FPM. A bit after that the First Officer/PM looked at the maintenance log about the Deferred Maintenance Item (DMI) for the super glue used to permanently attach the RAM mount to the window. We started discussing the problems the glue caused still stuck on the window. When the FO was done with the maintenance log I took it and looked at the DMI again. I then started to fill in the out/off and passenger count in the daily log. The FO was looking at info on his iPad.A moment later the FO says hey you're getting slow. I immediately [took] the controls and lowered the nose to increase the airspeed. As I lowered the nose the airspeed started to increase and I started to pull back again on the controls in order prevent a descent; we were around 31;500 feet; but my elbow slipped a little on the arm rest causing the control to jerk up a little. This quick jerk cause the Pitch Limit Indicator (PLI) to momentarily pop up; the stall warning tape to shoot up quickly and the shaker to activate for about 1 second and then just as quick they all went away again and the stall tape fell back down. The speed continued to increase and once the speed was back above green dot we resumed our normal climb and rate in FLCH. We lost around 200-300 feet in the maneuver.


Second narrative: [Report Narrative Contained No Additional Information.]


Synopsis: The crew reported that they were climbing in vertical speed; were distracted and became a little slow. They recovered but the stick shaker activated momentarily during the acceleration.
Date: 201305
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: EMB ERJ 140 ER/LR
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ramp ZZZZ
Aircraft component: Fuel System
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: Person Gate Agent / CSR
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Exterior and interior preflight items were normal. Completed engine start checklist and notified ground crew we were ready for pushback. Agent in charge notified me of a substantial fuel leak from Engine 1. I stopped the pushback to investigate. This was prior to engine start. Engine 1 was leaking a drop per second with fuel pump ON. Once pump was turned OFF; the leak eventually slowed. Maintenance was notified along with Dispatch and the problem was noted in the logbook. Kudos to the professionalism and safety-mindedness of our ground crew; especially the agent in charge. Fuel leaks are very dangerous and their attention to duty are part of what makes our airline one of the safest in the industry. Thank you very much!Unknown maintenance malfunction; suspect problem is related to fuel pump turning ON; pressurizing fuel system. Leak slowed once pump was turned off. Good job on part of ground crew. Need better communications with Dispatch and Maintenance [at foreign airport]. System did work; but it was highly inefficient.




Synopsis: An EMB-140 Captain; while at the gate and just prior to pushback and engine start; was notified by the Agent in charge that a fuel leak had been detected emanating from the #1 engine. It was noted that the leak was one drop per second with the fuel pump on; and slowly dissipated with the fuel pump in the off position.
Date: 201709
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Test Flight / Demonstration
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Autoland
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I wrote up a functional check flight as unsuccessful due to a bounce on landing during which I disconnected the autopilot and manually completed the landing. As I occasionally do; I checked the database to see what might have been wrong with the aircraft. The balancing entry stated that the autoland was disconnected at 2188 ft (1500 AGL). This not what I saw.


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


Synopsis: MD80 flight crew reported an unsuccessful autoland during a functional check flight.
Date: 202008
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Human factors: Situational Awareness; Communication Breakdown; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged
Contributing factors: Airport
Primary problem: Airport

Narrative: Upon arrival into ZZZ airport we got to our gate; A jet bridge was present. I understand maintenance was called for assistance with the jetway. Once maintenance arrived they were able to fix the jet bridge and it came to the aircraft. I followed procedures for disarming the doors (monitor & challenge) and then a thumbs up to the agent when they knocked on the door. We started deplaning; I was saying my goodbyes and watch your step to my passengers when to my horror the jetway started moving away from the aircraft fast. I immediately stopped deplaning and tried to close the door but it was too late the wheel that sits on the aircraft for movement was already in the doorway. The jetway ended up crushing the door. Maintenance came back of course and it took awhile to get the jetway unattached to the door. I was told that they were going to push the aircraft forward to realign with the jetway. However they ended up pushing the plane off the gate with the door open and moved us to another gate. This happened without warning or time to arm the doors.[In the future;] try and have an agent down when passengers are deplaning so that if the jetway starts to move they can stop it. I've never seen this happen so I'm open to learning what I could've done to prevent this.




Synopsis: Air Carrier Cabin Crew reported a malfunction with Jetway during passenger deplaning that resulted in damage to the aircraft.
Date: 202001
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
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate; Routine Inspection
Result: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: When processing Aircraft X inbound mail we found a piece of Priority mail with Dangerous Goods label and label that indicated surface transportation only. Mail looks to have come out of a larger postal bag of priority mail due to know presence of a airline DNR barcode.




Synopsis: Ramp employee reported finding USPS mail cargo labeled 'Surface Transport only' during aircraft cargo unloading.
Date: 201712
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Security
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Company Policy

Narrative: I am encountering an alarming increase in the number of flight attendants that have no knowledge of the SOP's regarding flight deck access via a Boeing keypad door. On today's flight; not a single flight attendant out of the four working flight attendants knew the SOP for normal flight deck entry via the keypad. More surprisingly and worrisome is that none of the working flight attendants knew the Emergency Access Code for the door! I asked each flight attendant; prior to boarding; to practice entering the normal entry code and the Emergency Access Code. It took several attempts by each flight attendant to be able to properly enter either code! We must do a better job training the flight attendants in proper SOP for flight deck access via Boeing keypad entry!




Synopsis: B737 Captain reported that flight attendants do not have knowledge of the SOP to gain access to the flight deck using the keypad.
Date: 201305
Local time of day: 1201-1800
Location: MMU.Airport, NJ
Weather elements / visibility: Haze / Smoke; 10
Aircraft: BAe 125 Series 800
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class E N90
ATC / advisory: TRACON N90
Aircraft component: Autopilot
Component problem: Failed
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer; Flight Crew Multiengine
Human factors: Other / Unknown; Workload; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Overshoot; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Hawker 800 was on vectors heading 280; and had been given a climb to 14;000. Aircraft was light and was climbing fast. Departure Controller issued a clearance direct to Solberg (SBJ) VOR to pick up our route (V3) back down to Baltimore. The direct clearance; and level off occurred nearly simultaneously. Undetected by both pilots; the left Automatic Flight Control System (AFCS) had failed. The failure had occurred while the aircraft was in heading mode and vertical speed mode; so the aircraft continued on its heading and at its last climb vertical speed. Neither pilot remembers hearing an autopilot disconnect warning. Pilot flying was investigating why the aircraft was not responding to the turn towards Solberg. At 14;200 FT pilot not flying realized aircraft was climbing through its assigned altitude and that the autopilot had failed. Pilot not flying called the discrepancy. Pilot flying halted the climb at 14;350 FT and began slow descent back to 14;000; and initiated a turn to SBJ. ATC Controller called to confirm the aircraft was stopping climb at 14;000 FT. There were no other aircraft in the vicinity of the incident (At least nothing on TCAS). Pilot flying continued flight with no further incident. Contributing factors; both pilots have been flying only once a week; and on short duration flights. Scans have slowed. Momentary task saturation as turn; level off and autopilot failure occurred (or at least was discovered) at the same time. Hard failure of left AFCS.




Synopsis: Hawker 800 Captain experiences an autopilot failure; without warning; at precisely the time the aircraft needed to level off and turn to a fix. An overshoot occurs which is quickly corrected. Infrequent flying on short trips was cited as a factor in the incident.
Date: 201209
Local time of day: 0001-0600
Location: LAS.Airport, NV
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
ATC / advisory: Tower LAS
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe
Detector: Automation Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I had a loss of separation because of the misapplication of visual separation. New procedure in place at LAS is called ADW (Arrival and Departure Window). Right before I was to take the Local 1 position I had a discussion with my supervisor regarding the potential for an aircraft to roll through the intersection while I was departing; fully complying with ADW; thus having two aircraft; both an arrival and departure on the same runway. He expressed to me he was under the impression it would be a negative situation; I believe he said runway incursion but I am not positive; but he indicated it was not legal to have two aircraft on the same runway in that situation we were discussing. Wouldn't you know later while working Local 1 applying ADW procedures (complying with all aspects to the best of my knowledge) an aircraft rolled to the end of 19R with traffic departing 25R. ASDE-X warnings screamed about converging traffic. I was very shook up and asked my assist to relieve me as my voice was shaking audibly on frequency. At the time of this incident I had traffic an A320 airborne and a B737 rolling. Before I cleared the B737 for takeoff with out delay I asked pilot to report previous departure in sight. He read back 'cleared for takeoff no delay maintaining visual separation with previous aircraft'. In between these two departures [I was] appropriately applying procedures per our 'rules;' I ended up with a departure and arrival on the same runway and ASDE-X screaming about converging traffic. Trying to keep my composure as I requested relief; I shipped the B737 to Departure without reiterating 'approved' or 'maintain visual separation'. Decide what your rules are before implementing a new procedure. Brief your employees properly; starting from the 'top down'. I feel the alarm from the ASDE -X; coupled with the conversation with my Supervisor led me to not close the loop. I was concerned I had done something wrong in applying our ADW procedures. I will also re-evaluate the phraseology and timing of when I request/approve visual separation.




Synopsis: LAS Controller experienced an ASDE-X event when Runway 25R landing traffic and rolling across Runway 19R activated the alarm due to departure traffic from Runway 19R; the less than clear ADW procedures were listed as contributory.
Date: 201910
Local time of day: 0601-1200
Location: EWR.Airport, NJ
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B EWR
ATC / advisory: TRACON N90
Reporter organization: Air Carrier
Human factors: Situational Awareness; Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Speed All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Procedure; Human Factors
Primary problem: Procedure

Narrative: Approximately 20 miles SW of RBV inbound to EWR; and level at 10000 feet and about 305 kts; we received a clearance from ATC to; 'descend to 7000 and keep your current speed below 10000 to 7000. I'll tell you when to slow'. We confirmed the clearance and I started a descent to 7000 at 305 kts. After several minutes at 7000 we received a hand off without a speed reduction. We queried the next controller about our speed and his response was; 'I don't care'. At that point I slowed to 250 kts. The rest of the flight was uneventful. It wasn't clear to me at the time that ATC is not authorized to clear me for a speed above 250 below 10000 feet and I should have rejected the clearance.




Synopsis: ATC controller directed a B-737 crew inbound to EWR to descend to 7000 ft during the arrival and to keep the aircraft speed at 305 knots below 10;000 ft altitude.
Date: 201509
Location: ZMP.ARTCC, MN
Flight conditions: VMC
Light: Daylight
Aircraft: Bonanza 35
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class A ZMP
ATC / advisory: Center ZMP
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Critical; Airspace Violation All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was flying VFR using oxygen through a cannula and GPS navigation and became confused and unable to restore my GPS receiver to the flight track page. During this time; the aircraft apparently climbed to 18;400 feet although I did not realize it at the time. I was using radar flight following and the controller asked me to descend. Once at an altitude under 10;000 feet; he told me that he as well as other pilots listening on the frequency believed that I had become hypoxic. I acknowledged that it was possible; but was regularly checking my oxygen flow which indicated sufficient for 18;000 feet.I received a call today from FAA notifying me that I had a Class Alfa incursion which surprised me because I have no recollection whatsoever of being told that by the radar controller. That pretty much convinces me that I was indeed hypoxic without realizing it; since the FAA representatives heard me notified on the taped conversation. At this point I don't really understand how it could have happened with the flow meter indicating as much as it did. I will inspect the cannula to see if there might be a leak somewhere downstream of the flow meter. I routinely inspect the cannula and hoses; but realize that I must inspect them much more carefully in the future. I always carry a spare cannula for just such a situation; but it never occurred to me that I needed it when I actually needed it; if it turns out to be the problem.




Synopsis: BE35 pilot reported he experienced a Class A airspace incursion possibly because of the effects of hypoxia.
Date: 202012
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Confusion; Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: As I am greeting passengers and handing out wipes; Passenger X seated in X; boards the aircraft with mask barely covering his nose or mouth; him and his family. I gently as them to please cover nose and mouth to board; they comply. Keep in mind even kids barely have mask. They all boarded with mask on chin. When they get to their seats they still have it on. Now after pilots inform us that we are departing; Passenger X completely takes off his mask; passengers around him are looking uncomfortably anxious and he is looking to see if I am can see him.  Although the lights are dim in the cabin I can still see him and he sees me. I do a friendly gesture so he can put it on. He completely ignores me. Then when I get the 10;000 I get up to kindly ask him to place mask over nose and mouth; he complies and then as I walk away he takes it off. I let him know one more time announcements say. He doesn't comply and wife [has] her mask off too; to tell me why don't I leave him alone. At this point I head towards forward to inform pilots and they let me know to let him know one last time. When I informed him I spoke to the pilots and then finally after three gentle reminder; he and wife and kids comply.




Synopsis: Flight Attendant reported a passenger was not compliant with face mask policy.