elihoole/asrs-aviation-reports huggingface dataset:
Date: 201902
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation III; VI; VII (C650)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Corporate
Reporter function: First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Procedure; Human Factors; Aircraft
Primary problem: Aircraft

Narrative: Current aircraft operator did not have RVSM authorization letter. When we reached the cruising altitude of FL280 we found that we were in the tops of a cloud layer and it was choppy there. We asked for higher and reported negative RVSM. Center cleared us to climb to FL320. When Center handed us off to [the next Center controller] we checked in negative RVSM. [The next Center] told us to descend to FL280 and call a number about a possible pilot deviation.I found out that we are not supposed to be allowed to cruise at an RVSM altitude without RVSM approval. I thought the controller could let you into RVSM airspace traffic and workload permitting; but that is actually only to climb or descend through RVSM; not cruise in it.




Synopsis: C650 First Officer reported being non-RVSM; yet ATC allowed clearance into RVSM airspace.
Date: 201904
Local time of day: 1201-1800
Location: 3B3.Airport, MA
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke; 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZBW
ATC / advisory: Center ZBW
Second aircraft: Sail Plane
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After leaving [my departure airport]; I received ATC flight following [en route to ZZZ]. Everything was fairly normal. I received some minor traffic advisories.Just before Sterling (3B3); flight service provided a traffic advisory. I can't remember the exact wording but within a second or two I noticed traffic immediately to the right. A glider. I announced traffic in sight. It seemed like the glider made a turn towards me and I took evasive action turning left and descending. I did notice another glider. I can't remember whether the original glider was red and white or yellow. Those were the colors of the gliders.It seemed sort of close but at the time; I don't think I heard anything further from flight service and really couldn't judge the distance. When I was home later that evening; I paced out 500 feet and realized that the glider probably was within 500 feet. Therefore; I am reporting this incident.




Synopsis: PA28 pilot reported an NMAC with a glider while enroute.
Date: 201908
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Headset
Component problem: Improperly Operated
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: Communication Breakdown; Confusion; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Became Reoriented
Contributing factors: Procedure; Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Midflight just before the arrival briefing my Captain headset started to come in and out and I started to hear ATC and the FO (First Officer) intermittently. I knew right then and there; premonition by experience I guess; that this was not going to end well and that I should immediately start to look for threats. But all was going smoothly until the intercept of the localizer when I asked the FO if he was going to intercept the localizer and he even shallow the intercept angle; but the runways are so close apart that; that we did not notice that we were more lined up with Runway XXL then Runway XXR as we got closer Tower asked us if we were on Runway XXR and at that moment we realized that Captain was on the Runway XXR and FO was on the Runway XXL frequency. We immediately decided as a crew to look outside and ignore what the instruments were telling us. At that moment we thought it was a navigation problem and not a pilot error problem. We ended up landing on the right runway and no further error were noticed. 	Cause of the event was unknown headset/communication issues and close adjacent runways; as well as improperly selected and cross checks frequencies. Having a spare company headset with microphone could have averted this event; as I did not hear the frequency that the FO had selected on his side. I was busy trying to make out what he was saying and troubleshoot the headset and headset connection. We take for granted how a quiet and well sounded the cockpit is in normal events.




Synopsis: CRJ 700 Captain reported that communications issues led to setting up for the wrong runway.
Date: 201511
Local time of day: 0001-0600
Location: ORD.Airport, IL
Flight conditions: VMC
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ground ORD
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown; Time Pressure; Workload
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight; Taxi
Result: Flight Crew Took Evasive Action; General Physical Injury / Incapacitation
Contributing factors: Airport; Company Policy; Human Factors; Procedure
Primary problem: Company Policy

Narrative: Had a passenger pass out and hit is head on the rear galley counter. Tended to by onboard EMT and flight attendants; as it was uncertain if he suffered a minor seizure. Coordinated with Medlink and dispatch to continue to ORD and have paramedics meet aircraft; once he improved and was stable. 30 minutes prior to landing; sent a message to ensure paramedics would be there. Told that they would. Arrived at [the gate] and no paramedics and no jetway driver. No communication possible from ramp/operations. Eventually paramedics show up; but unable to access aircraft. Eventually; they pushed us back; and we taxied to [a different gate.] Blocked in XA:49; and called dispatch to correct incorrect time of XA:29. In operations; still had wrong time in [computer.] Spent 25 minutes on hold between Dispatch and Flight Duty Manager (FDM). Finally FDM says he sent a message for 15 minutes of taxi pay. I said that the records should say that as well; and he claimed no; it was considered just a reposition. Told him that was not correct; and told to file a report. Just terrible communication and handling. Apparently the airport had worked on [the first jetway]; and knew the jetway was out of service; and nobody noticed; before assigning it to our flight. Medlink was supposed to have paramedics waiting; and they were not.


Second narrative: I have had numerous issues in ORD with parking in the last year. They are always embarrassing and extremely frustrating for all involved. However; this event crossed the line from being an embarrassment to the company to potentially putting the health of our passengers at risk. Our passenger was stable; and the paramedics were called as a precaution; what if this was a more serious medical condition and he needed immediate assistance. We would not have been able to provide him help.


Synopsis: A flight crew with an injured passenger on board requested EMT assistance upon arrival. However; the aircraft was parked at a non-functional jetway with no EMTs and was towed to another gate. Inattentive ground operations puts people at risk.
Date: 202008
Local time of day: 1201-1800
Location: D01.TRACON, CO
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E D01
ATC / advisory: TRACON D01
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: On the LONGZ 1 Arrival into DEN; ATC said they had a reroute for us and to let them know when we were ready to copy. I as the PM (along with the PF concurrence) said 'go ahead.' ATC said 'proceed direct to HIPPE and then pick up the FLATI 1 Arrival to DEN.' He phonetically spelled out the intersection to proceed to; and I read back (or thought I read back) HIPPE. The PF put HIPPE into the FMC and I verified before execution and said it was correct; he executed and then started programming the FLATI 1 into the FMC. At that point; ATC asked where we were going; and I said to the intersection 'HIPPE;' and repeated it out phonetically and he said it was 'HIPEE' and repeated it phonetically. We programmed HIPEE into FMC; executed and then put FLATI 1 Arrival into the FMC and proceeded to DEN. ATC did not say that there was any loss of separation; and we proceeded to DEN and landed uneventfully. These two intersections sound exactly alike and are both in the region. Maybe one of these intersection names needs to be changed because I could see this mistake happening again.




Synopsis: Air carrier Captain reported a track heading deviation during arrival to DEN airport after confusing similar sounding fixes HIPPE and HIPEE.
Date: 201910
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Cabin Furnishing
Component problem: Improperly Operated
Reporter organization: Corporate
Reporter function: Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Second reporter function: Flight Attendant (On Duty)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate; Pre-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Procedure; Chart Or Publication; Human Factors; Aircraft
Primary problem: Chart Or Publication

Narrative: I'm writing to you about my flight I took over in ZZZ. I worked [flight] and my girls noticed this sign on the over wing exit door. We as flight attendants are trained to brief the exit row people to open the door then throw the door forward the wing. This sign was on the door and it says to place the door on the seats after they open it. Thought we bring that up to you guys.Another thing was the bag issue we had on the plane. Aircraft came in with over sized bags not stowed properly. We had bags strapped into seats. When we boarded our passengers; myself and my flight attendants worked hard to get all these bags stowed to the best of our ability to FAA standards. If you need get in touch with me feel free to email me. I probably won't return calls but when I get to my hotel in ZZZ; I surely will return any calls or emails. Thanks again for your time.


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


Synopsis: Flight attendant reported exit door placards are out of compliance and that over sized baggage was stored improperly in violation of FAA regulations.
Date: 202112
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Dusk
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZZ
ATC / advisory: Center ZZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Confusion; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Inflight Shutdown; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise flight (FL320) en route to ZZZ the left engine began to spool down. N1; N2; and fuel pressure began to drop. The aircraft lost power and began to slowly drift down. Very soon after we received a L FUEL LO PRESS caution message. We decided to request priority handling and requested a lower altitude. We were given descent to FL260 and direct ZZZ. I was the pilot monitoring and the Captain transferred controls to me in order to run the QRH. He ran the procedure for L FUEL LO PRESS which was ineffective. We could not find any other appropriate procedure in the QRC or the QRH. We then attempted a windmilling relight even though we felt that it would not work without fuel pressure to the engine. We also attempted to restart with the APU below 13;000 feet; which was also unsuccessful. At this point; we were very close to ZZZ and performed an inflight engine shut down. After securing the engine we prepared for the single-engine landing. The FA was notified and informed that we were performing a single-engine landing and what to expect. Then the Captain took control of the airplane and landed visually on [Runway] XXL in ZZZ. The landing was smooth and without incident. ZZZ tower had dispatched emergency vehicles and they followed us to the gate while we taxied back under our own power. Deplaning was normal. Cause - Fuel issue to the left engine. Troubleshooting was somewhat difficult after the QRH procedure was ineffective. We saw nothing else going wrong in order to reverse the situation. Maintenance wrote it up as a sheared pump drive shaft and it was replaced.




Synopsis: CRJ200 First Officer reported a #1 Engine spool down at cruise. The engine was shut down and the aircraft diverted to make a precautionary landing.
Date: 201511
Local time of day: 0601-1200
Location: FAI.Airport, AK
Flight conditions: VMC
Light: Dawn
Aircraft: Beech 1900
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class D FAI
ATC / advisory: Tower FAI
Reporter organization: Air Taxi
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation - Altitude Undershoot; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was the SIC on BE-1900c departing Fairbanks. It was VMC conditions; but we picked up an IFR clearance for departure. I was the pilot monitoring (not flying) on this flight. After takeoff we climbed at a slow rate; because we were planning on cancelling IFR once out of the Fairbanks area. The tower controller at one point addressed us (to the effect of) what are you doing; we then realized we were tracking 20 degrees left of course. We cancelled IFR at that time and proceeded VFR from then on. The same Controller moments later gave us a phone number to call before we got clear of TRSA services. We called on the ground and were told that we may have been below the minimum climb gradient for an IFR departure out of Fairbanks.




Synopsis: BE-1900C First Officer reported departing Fairbanks and being advised by ATC that they were off course and below the minimum climb gradient.
Date: 201812
Local time of day: 1801-2400
Location: LAX.Airport, CA
Light: Night
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class E SCT
ATC / advisory: TRACON SCT
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Departing LAX on the LADYJ 4 SID; I was the FO; PF (First Officer; Pilot Flying). As a relatively new First Officer; I was unfamiliar with LAX. Due to time constraints from an unscheduled aircraft swap; the Captain rushed through the briefing and did not give me an opportunity to brief the departure. I interjected to discuss a separate issue with the departure; an 'at or below' versus MCP selected altitude; which was resolved; but I did not adequately brief the entire procedure to include the 'MAINTAIN 250 UNTIL ADVISED' note. This constraint was not in the FMC.Climbing through 13;000 feet; (CMD B engaged); ATC queried our speed; which was 305 KIAS. As the Captain/PM (Pilot Monitoring) responded to the query; he simultaneously selected LVL CHG on the MCP and yanked back on the thrust levers. I was immediately confused as to who was flying the aircraft; if he was taking the aircraft or if I was still flying. I did not understand why he did not ask or direct me to make the change as PF. The situation was resolved and we continued to [our destination] uneventfully.An adequate Departure Briefing is mandatory. As the FO; I should have been more assertive in requiring us to slow down and properly brief the procedure. This would have eliminated the speed error after departure. To mitigate confusion during flight; I believe positive exchange of flight controls should always be used. Any time saved in correcting this speed error by the Captain manipulating the MCP was; I believe; negligible.




Synopsis: B737-800 First Officer reported an inadequate pre-departure briefing led to an airspeed deviation departing LAX.
Date: 201605
Local time of day: 1201-1800
Location: EGLL.Airport, FO
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Second aircraft: Large Transport
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Captain; Pilot Flying
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Police / Security Involved
Contributing factors: Human Factors; Airport; Aircraft; Procedure
Primary problem: Ambiguous

Narrative: After arrival; while boarding bus to hotel the Captain was approached by a local Constable. The Constable advised the Captain that the ground crew loading/unloading a narrow body aircraft on a hard stand [behind our aircraft and roughly 400 feet north] thought that jet blast from taxi in could have caused a cargo container to be displaced from the loader. Normal procedures were used during taxi in. EGLL ground did change our gate because ours was occupied.


Second narrative: I was Captain of a B777 flight to LHR. While taxiing in to our originally assigned gate; we were reassigned to park at [the adjacent gate]. I started my 90 degree turn onto the gate lead-in line at approximately 7 knots and idle power. This was enough energy to continue to the stop point with the engines still at idle until we parked.After deplaning; while awaiting the crew bus to the hotel; I was approached by a Constable. He advised that a ground crew unloading baggage bins from a [narrow body aircraft] at hard stand 355 alleged that the jet wash from our aircraft had blown a cargo container off the raised cargo loader onto the ground; striking the [narrow body aircraft] in an unknown location. The constable took the particulars of our flight along with my name and employee number. As we left for the hotel; our crew bus passed very close to the aircraft in question; and various members of my crew took photos. Some of these photos show the location relationship between our aircraft and other aircraft; while others show the cargo bin on the ground next to the [narrow body aircraft].After examining the LHR parking diagrams; along with aircrew and Google Earth photos of the parking gate and hard stand positions; it is difficult for me to imagine jet wash from engines at idle while parking at the gate impacting hard stand 355. If indeed the allegations are correct; then it would seem there are only two possible solutions to keep such an incident from happening again. First; prohibit wide body aircraft from parking at the gates when hard stand 355 is occupied; or secondly; prohibit use of hard stand 355 when wide body aircraft will be using the gates.


Synopsis: Flight crew is informed after parking at their gate that jet blast from their aircraft may have caused a cargo container to fall from a loader and damage the aircraft being loaded.