elihoole/asrs-aviation-reports huggingface dataset:
Date: 202001
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: Flight Attendant (On Duty)
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Pre-flight
Result: Flight Crew Overcame Equipment Problem; General Release Refused / Aircraft Not Accepted
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During passenger boarding a catering representative placed two carrier boxes filled with dry ice right in front of the boarding door; stating that the crew should take this on the aircraft because of an inoperative chiller. The crew was; at that moment not aware of any inoperative chiller on the aircraft. During the briefing with the Captain; and after checking the list of maintenance issues in my link; there was no mention about an inoperative chiller. The two carrier boxes posed a significant tripping hazard to our customers boarding; but the catering representative refused to remove the carrier boxes; stating that the flight attendants should take them on board. The carrier boxed where too heavy to lift; and it is my understanding that we should not carry heave carrier boxes full of dangerous goods through an aircraft with customers on board. An In-flight Supervisor was in the area and was unhelpful in resolving this dangerous situation. While I was trying to have these carrier boxes with dry ice removed; this Supervisor displayed aggressive behavior and stating if I was refusing the dry ice and taking a delay. He was unwilling to listen or understand the problem with having two carrier boxes full of dry ice being placed in front of the boarding door while customers were boarding. At this point I was informed by the Captain that chiller number 7 in the aft galley had an issue and the fuse was pulled. No one informed the crew about this. In the interest of departing on time; and to satisfy the Supervisor who was getting more hostile by the minute; I decided to accept two bins of dry ice; that I hand carried on the aircraft myself. We then were able to close to boarding door and leave on time.




Synopsis: Flight Attendant reported that a communication breakdown resulted in dry ice being brought onboard the aircraft without proper documentation.
Date: 201509
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Second reporter function: First Officer; Pilot Flying
Anomaly: Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General Physical Injury / Incapacitation
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Descending into [destination] and leveling at 11;000 feet; moderate turbulence was encountered and 3 flight attendants were injured.  Airplanes in front of us did not mention any turbulence and we were not deviating for the weather.


Second narrative: On arrival we had been told to expect only light chop in the descent and had the seatbelt sign on. As we entered a small cloud layer between two cells barely displaying on our radar display we encountered about 3 seconds of moderate turbulence. We called back to check on the Flight Attendants to find that two had fallen and had hit their head. Not knowing the severity of their injuries we [contacted ATC] when ATC gave us a delay vector to ensure expeditious handling to the airport. We also requested an inflight supervisor and paramedics meet us at the gate to err on the side of safety.


Synopsis: A B737 flight crew reported they encountered unforecasted turbulence and several flight attendants were injured.
Date: 201903
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Ramp
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Security
Detector: Person Ground Personnel
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: After my Dispatcher disconnected the tow bar; the pilot informed him that a passenger believed that their last minute checked carry on was loaded with a lithium ion battery that they failed to remove prior to boarding. We returned the aircraft to the gate to retrieve the bag. Once parked; my crew pulled the bag off the aircraft; scanned to offload it; and were holding it planeside. While I was helping my pit guy close up the FWD pit; Supervisor took the questionable bag from the planeside; and breached security by not only taking the bag upstairs and crossing the threshold of the secured area; but also leaving it unattended in the jetbridge. When I realized what had happened; and confronted [supervisor] about the breach in FAA protocol; he said he knew that he was not supposed to bring the bag up; but did so anyway.




Synopsis: Ground employee reported removing passenger luggage from cargo due to Hazmat restriction. Reporter also noted FAA security breach by leaving baggage in unattended on the jetbridge.
Date: 201301
Local time of day: 1801-2400
Location: BWI.Airport, MD
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Night
Aircraft: B717 (Formerly MD-95)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class B DCA
ATC / advisory: TRACON PCT
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Chart Or Publication; Procedure; Human Factors
Primary problem: Ambiguous

Narrative: During descent into Baltimore on the RAVNN RNAV STAR we were vectored off the arrival numerous times and given assigned airspeed changes. After being vectored off the arrival we were cleared direct to OTT; cross OTT at 9;000. Neither the Captain nor I ever heard 'Descend via the RAVNN arrival.' We complied with the clearance to cross OTT at 9;000 and subsequently switched controllers. The next Controller asked if we were going to make RAVNN at 6;000. We told him that; although we had not heard a clearance to 'Descend via' the arrival; we would descend to 6;000. The Controller then cleared us to 'descend to 6;000' and never mentioned anything further about missing an altitude. No further incident occurred. In the future; when being vectored off the arrival and checking in with a new controller; it is would be wise to check with the new controller to make we are all on the same page as the previous controller. This way you know what is expected of you.




Synopsis: After they had been vectored off of and then returned to the RAVNN RNAV STAR to BWI; the flight crew of a B717-200; as well as the Controller to which they were switched; were uncertain as to whether or not they had been 'cleared via' the STAR and were intending to comply with the STAR restrictions.
Date: 201201
Local time of day: 1201-1800
Location: TEB.Airport, NJ
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: BAe 125 Series 800
Operator: Corporate
Operating under: Part 91
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class B EWR; Class D TEB
ATC / advisory: TRACON N90
Reporter organization: Corporate
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Human-Machine Interface
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
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: [We were on the] RUUDY 4 RNAV departure out of TEB Runway 24 to cross WENTZ at 1;500; then cross TASCA at 2;000. We cross WENTZ at 1;500 and than started our climb to 2;000 just passing WENTZ. TEB Departure called and gave us a new heading and a higher altitude and said we started our climb to 2;000 just before crossing WENTZ and then gave us a frequency change. Not sure what caused the problem. We know the problem with the Newark arrivals descending over Teterboro Airport. As this is a RNAV departure; we have no other way on this SID to identify WENTZ; TASCA and RUUDY waypoints. We briefed for the departure; setting up the FMS for this SID and using VNAV. I was hand flying the airplane and at 1;500 noticed that the flight director was still calling for a climb. At WENTZ we then started our climb to 2;000. What could have caused the problem? VNAV not selected on the flight director or VNAV drop off after takeoff? We seldom do VNAV departures and in the future need to verify VNAV is selected.




Synopsis: A HS125 pilot was admonished by ATC for starting to climb to 2;000 FT just prior to WENTZ on the RUUDY 4 departure from TEB.
Date: 201208
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Learjet 35
Flight plan: IFR
Flight phase: Landing
ATC / advisory: Tower ZZZ
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Local Controller issued improper restricted low approach instructions to a Skyhawk and did not receive a read back. The aircraft did a touch and go and departed while a Lear was at the main intersection of the crossing runways and over flew the Lear. Local Controller should follow proper procedure for restricted low approach clearance and recognize when to issue go around instructions when loss of separation was imminent.




Synopsis: Tower Controller reported a loss of separation when the Local Controller failed to secure a correct read back resulting in an overflight of traffic at an intersection.
Date: 201708
Local time of day: 0601-1200
Location: MMQT.Airport, FO
Flight conditions: Marginal
Weather elements / visibility: Haze / Smoke
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: Broke out of VOR approach Runway 9 MMQT near minimums; autopilot on with LNAV/VNAV. Approach was busy but not overwhelming. Mistook ground feature/structure that looked like a runway with a parallel taxiway (approx two miles short of runway) for the airport and attempted to line up on that 'runway' with autopilot/autothrottles disconnected. Kept wondering; 'Why does this airport look so strange?' Obviously because it was not a runway/airport. The First Officer said; 'Do you see the runway out there?' (approx 300 AGL) At the same time I looked further out and identified the runway with four red on the PAPI; we received a 'TOO LOW; TERRAIN' warning. I immediately added power to correct to the proper glide path and continued to a normal landing.




Synopsis: Large Transport Captain reported difficulty locating the runway at MMQT and receiving a 'Too Low; Terrain' warning.
Date: 201308
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: Cessna 152
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Climb
ATC / advisory: TRACON ZZZ
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Government
Reporter function: Approach; Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: A Cessna 152 called for his IFR release. I read him his clearance to ZZZ; the flight plan I had was from ZZZ1. I had him hold because of traffic at ZZZ1. After the traffic was clear; I released him. I was vectoring a Cessna 172 for an approach at ZZZ. I switched the C172 to advisory frequency and gave a position relief briefing; during my two minute overlap I noticed that the aircraft I released off of ZZZ1 was actually departing ZZZ. I then saw that the C152 had a flight plan off of ZZZ as well. This event has made me much more aware of my strip management; and to be more thorough in checking if someone has two flight plans in the system; also I will probably always have them state what airport they are departing.




Synopsis: TRACON Controller described an unsafe event when releasing an aircraft from an uncontrolled airport only to find two flight plans were filed off different airports and the wrong departure was being considered for the release.
Date: 201903
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: During descent info ZZZZ; above approximately 10;000 feet; we detected an odor. We were just cleared to slow to 220 knots; and when the power went to idle; the Captain stated he smelled something similar to burning rubber; and asked me to check with the flight attendants in the galley. I called door 1L; and they did not smell any odors; and they verified that they weren't burning anything. As I called them I detected the odor as well. It was initially strong. Enough to get an acrid taste in my mouth. Just as quick as it began; the odor dissipated. Out of an abundance of caution; and to make myself useful; I stood up and checked our luggage and the rest of the cockpit. I checked the floors and vents for any odors and there was none. The Captain asked what I was doing and asked if I checked the luggage. We then focused our attention on the approach. On rollout we briefly detected the odor again. We discussed that we would expect a possible odor then after using the brakes and thrust reversers. After block in; the Captain asked us if we think the odor warranted any additional investigation. We all agreed the next crew should be aware; and a log entry should be entered for tracking purposes. I thought Maintenance should at least check the areas we don't have any access to. When Maintenance arrived; the first thing they asked was if we had any Hazmat. One of the employees in Operations discovered a cargo container with leaking Hazmat. A battery had leaked onto plastic; causing the smell. One of the shipping pallets was broken. We went outside and determined that it indeed was the exact odor. The ground crew unloaded all of the cargo for the inspection of the area around the damaged Hazmat. No traces were discovered. Everyone involved went the extra step to ensure the safety of the outbound aircraft. We stayed an extra couple of hours to help as much as we could.




Synopsis: B767 flight crew reported fumes on flight deck on descent for landing. Post flight Maintenance reported Hazmat cargo spill in cargo compartment.
Date: 202102
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Other unknown
Flight phase: Other Parked pre-departure
Aircraft component: FMS/FMC
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Procedure; Aircraft; Human Factors; Software and Automation
Primary problem: Human Factors

Narrative: I believe this aircraft had been parked due to COVID.  Apparently; when pulled out of parking; the FMS database was not updated.  During pre-flight we noticed that revision 'W' and 'X' were available; but revision 'Y' was now current.  I don't know how long this plane has flown without 'Y' database; but it is deferred now.




Synopsis: Air Carrier Captain reported the aircraft database was a few revisions 'out of date' and suspects the aircraft was 'parked' during the pandemic for an extended period of time.
Date: 201207
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Cessna Super Skywagon/Super Skylane
Flight plan: IFR
Flight phase: Descent
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Approach; Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Aircraft

Narrative: Training on sector; a C206 advised 10 NM south of the airport; he was low on fuel and requested priority. The trainee told the pilot he would get it and turned the aircraft he was to follow out for new sequence and descended the C206 from 5;000 to 3;000. Trainee then amended the descent to 4;000 due to the traffic ahead. Due to frequency congestion two partial transmissions came from the C206 apparently requesting to be turned towards the airport. Trainee descended the C206 again to 3;000 before realizing a B737 was too close behind at 3;000 and told the C206 to maintain 4;000. Both of these altitude assignments went unanswered. The C206 instead stated something like 'engine at idle and don't know if it will stay running.' Trainee did not respond to the C206; but made 2 other transmissions. I took the frequency when I saw the C206 descending and turned and descended the B737. I assumed the C206 was unable to maintain level flight since he had not acknowledged the clearance to 3;000. I turned the C206 towards the airport and asked if he could make the field. He said he could and had the field in sight. I issued a visual approach clearance and asked his condition. He said everything was operating normal. The pilot of the C206 clearly had issues. From the time he asked for priority due to low fuel until it sounded like he engine was going to quit was less than 5 minutes and 10 flying miles. He should have been able to realize sooner he may be in trouble instead of waiting until it was almost too late.




Synopsis: TRACON Controller providing OJT described a confused 'low fuel' event when inbound general aviation traffic indicated the need to fly toward the airport with all haste. The reporter listed the need for cleared communications between the pilot and ATC would have prevented this incident.
Date: 201411
Local time of day: 1801-2400
Location: IAD.Airport, DC
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other All
ATC / advisory: Center EISN
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: ATC Equipment / Nav Facility / Buildings; Company Policy; Procedure
Primary problem: Ambiguous

Narrative: There seem to have been major flight plan transmission errors with this flight.  Accomplished all normal international preflight planning and went to the aircraft with all flight papers in our possession.  The following problems showed up as we progressed through each phase of flight:No PDC at the gate.  Got our clearance via voice. No oceanic clearance via datalink. (Gander/CZQX).  Voice procedures used to obtain clearance.  Controller asked for additional items beyond the usual clearance request items. Cleared via track 'Y'. At 30 West (eastbound); lost ATC datalink.  Checked in with Shanwick Oceanic (EGGX) on HF.  They also required additional flight information beyond the usual clearance items.  Made one position report via voice; due to difficulty signing back on to CPDLC.  On handoff from oceanic to domestic controller (Shannon/EISN) additional information was once again requested.  At this point we received a major reroute from ATC; none of which was on our flight plan.  We queried the controller as to where we would rejoin our planned route of flight.  Her response was; 'I don't know; I do not have your flight plan.  You can ask the next sector.' At this point we contacted Dispatch via satcom.  Dispatcher stated that Dispatch is using a form of shorthand to file flight plans and that sometimes ATC facilities will reject this information in the different format. It would appear that we flew over 6400 NM with a very marginal; almost nonexistent; flight plan.




Synopsis: B777 First Officer describes difficulties with clearances on a flight from the USA to Europe. Initial clearance no PDC; obtained via voice. Oceanic clearance obtained via voice with many additional questions. CPDLC is sporadic and HF position reports are required. Shannon Control asks many additional questions and issues a major reroute without explanation. The Dispatcher indicates they are using a form of shorthand to file flight plans; which may be causing the difficulty.