elihoole/asrs-aviation-reports huggingface dataset:
Date: 202001
Local time of day: 1801-2400
Location: ZAB.ARTCC, NM
Flight conditions: VMC
Light: Daylight
Aircraft: Small Transport
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class E ZAB
ATC / advisory: Center ZAB
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure
Anomaly: Airspace Violation All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert
Contributing factors: Airport; Airspace Structure; Chart Or Publication; Human Factors; Procedure
Primary problem: Airspace Structure

Narrative: Aircraft X departed ALM; looking to pick up IFR to ZZZ1. Normally HMN Approach would issue this clearance; however; they were closed. When I issued the code and got him tracked up; I noticed he was on a southwest bound heading and had filed direct to ZZZ1. This was an issue; because that would put him straight through White Sands Missile Range (R-5107B/R-5107D). Therefore; I asked him if he was familiar with White Sands and the restricted airspace; he said he was not. At this point I let him know he had restricted airspace at his 12 o'clock in 1 mile and to turn flying H170. He made the turn and stayed clear of the airspace. I then asked him if he was familiar with the VFR corridor towards ELP; and he was also unfamiliar. I asked for a D-side at this point; which was then given right away. I issued a second vector to Aircraft X to turn him northbound out of the VFR corridor; and told him to remain VFR. I asked my D-side to put in a good route for the aircraft; so I could focus on my other traffic. Once Aircraft X was clear of the restricted airspace I issued IFR around R-5103 A;B;C and onward to ZZZ1. With an airport this close to restricted airspace; and the potential to depart straight west into it; how can an aircraft possibly be unaware. This isn't something I have witnessed a lot; but I would imagine there are several warnings this aircraft looked past to put him in this situation. If not there definitely should be.




Synopsis: A Center Controller reported an aircraft departed an airport requesting an IFR clearance but the pilot was not aware they were adjacent to restricted areas and heading into them.
Date: 202112
Location: JAC.Airport, WY
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Tower JAC
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Confusion; Distraction; Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: ATC Equipment / Nav Facility / Buildings; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: The ALPIN3 chart restriction at KICNE to cross it at 15;000 feet is incorrect per JAC ATC Tower. When queried the Controller clarified that it's supposed to be at or above 15;000 feet and that they have filed reports on this issue. The FMC database contains no restriction at KICNE.




Synopsis: Air Carrier First Officer reported an altitude shown on the JAC airport ALPIN3 SID chart; at the way-point KICNE; does not correspond to that given by the local ATC Tower.
Date: 201209
Local time of day: 1201-1800
Location: LAS.Airport, NV
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp LAS
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Chart Or Publication
Primary problem: Chart Or Publication

Narrative: We were told by LAS Ramp Controller to taxi to Spot 7. When I looked at the Commercial chart for Concourse D; I located spot seven and began a taxi to what I thought was that spot. As I arrived at the spot it was in fact spot 8. If you look at the chart you will see spot 8; not next to spot seven (where in fact it is) but half way down the chart. When I tried to call ramp to inform them of my mistake I noticed the First Officer had already switched to Ground and we then received a runway change and amendment to our clearance. I continued the taxi as I felt this was the safest course of action.

Callback: Reporter states that the current Commercial Chart diagram has corrected the discrepancy.



Synopsis: Air Carrier Captain reports that Spot 8 near Concourse D at LAS is not located where it is depicted on the Commercial Chart diagram.
Date: 202103
Local time of day: 0601-1200
Location: POU.Airport, NY
Aircraft: No Aircraft
ATC / advisory: Tower POU
Reporter organization: Government
Reporter function: Local; Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction
Anomaly: ATC Issue All Types; Ground Event / Encounter Ground Equipment Issue
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: ILS Maintenance and company; 2 vehicles; proceeded from the terminal to the approach end of Runway 6 to change a light near the threshold. ILS Maintenance correctly read back all instructions but due to the line of sight obstruction; the new academy hangar; was not visible for 6 minutes. While there was no conflicting traffic; had there been; we would have been unable to ensure that the vehicle was clear of the runway edge line.  Perform the necessary structural adjustments/changes to the academy hangar to allow for full visibility of the entire approach end of Runway 6.




Synopsis: A Tower Controller reported a new hangar being constructed blocks their view of part of one of the runways.
Date: 201912
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Confusion; Troubleshooting
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Not 100% sure. It doesn't seem like there is any rhyme or reason when fume events occur. The smell wasn't a dirty sock [smell]; but rather a hot metal type smell which threw me off. I suppose I could have aborted the Takeoff when we smelled it. Again; not having smelled the hot metal smell before; I wasn't thinking it was a necessarily a fume event at that exact second. Once I had a reaction to it; then I knew it was something abnormal.




Synopsis: A319 First Officer reported a fumes event during takeoff.
Date: 201911
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Aircraft component: Oxygen System/Crew
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Confusion; Time Pressure
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other Unscheduled maintenance
Result: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Troubleshot oxygen system all day for aircraft leaking crew O2 and not able to take any new O2. Replaced a transducer; ops checked bad; troubleshot it down to a broken regulator on the crew O2 bottle. Removed and replaced the O2 bottle yet misread the regulator saying closed instead of open.The crew tested O2 system with no oxygen coming out. Mechanics noticed regulator was wired in the OFF position. Was hurried to finish job due to unable to work late yet had to stay to complete job.Had a lapse of memory thought I re-secured the valve in the on position. Just made a mistake.




Synopsis: Maintenance staff reported that while repairing an inoperative Crew oxygen bottle; a valve was inadvertently secured in the wrong position.
Date: 201408
Local time of day: 1801-2400
Location: ZNY.ARTCC, NY
Light: Night
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZNY
ATC / advisory: Center ZNY
Second aircraft: Medium Large Transport
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Troubleshooting; Situational Awareness; Distraction; Communication Breakdown; Confusion
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: Procedure; Human Factors; Aircraft
Primary problem: Procedure

Narrative: Aircraft X and Aircraft Y departed via RBV.J230.  I climbed Aircraft X to FL280.  Read back was unclear; and the frequency was blocked.  I believed that Aircraft Y was making his initial check-in; but see he had already started to climb; so again I climb Aircraft X to FL280.  I continue my scan and see that Aircraft Z departing LGA to CYYZ via Newel was climbing at FL185 and was flashing with a Lendy arrival from Area C sector 36. I call N90 and see if they were climbing this aircraft.  They informed me that no and that he had been switched to my frequency.  I then descend Aircraft Z to 170 expedite for traffic.  I call sector 36; and advise him that I am descending my aircraft and that he must have taken another aircrafts instructions.  The sector 36 controller turned his aircraft to the left to avoid Aircraft Z and stopped his descent.  I did not recall the Aircraft Z checking on; but there must have been some frequency congestion and blocking and the wrong aircraft took the wrong instructions. First; there were many distractions for a good time before this incident.  There were many deviations by RBV and the N90 controller had to continuously call to coordinate deviations.  Also; similar sounding call signs were a factor.  Frequency congestion for deviations and also landline congestions for the extraneous coordination; it is sometimes difficult to keep the aircraft from blocking the check in.  If there are that many deviations; an in-trail restriction should go into place.  Companies should refrain from using call signs so similar because it causes unnecessary confusion.




Synopsis: ZNY Controller reports of similar sounding call signs causing confusion and pilots taking the others clearances.
Date: 201308
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: clear; 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Final Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Military
Reporter function: Instructor
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Flight Engineer; Flight Crew Multiengine
Human factors: Confusion; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During an instrument flight lesson we decided to add 10 gallons of fuel to meet the club requirements of 1 hour reserve. We requested 10 gallons of fuel with Ramp personnel; and the FBO front desk. We went in and flight planned and in approximately 1/2 hour we paid our fuel bill for 10 gallons and departed. We thought we had the fuel; but we experienced an engine out on short final followed by an emergency landing. Extensive damage occurred to the left wing and left horizontal stabilizer during the landing. We received a phone call from the FBO the next day stating that the fuel uplift was in error; and that we received only one gallon; as opposed to the ten gallons we paid for. This unfortunate oversight was directly responsible for the emergency landing and damage to the aircraft.




Synopsis: An emergency landing was conducted following fuel exhaustion on approach to landing; resulting in damage to the aircraft. An inadequate amount of fuel was added even though an appropriate amount had been requested and purchased.
Date: 201706
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 135 ER/LR
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Aileron Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Procedure; Aircraft
Primary problem: Ambiguous

Narrative: I was assigned PIC and the pilot flying. The weather condition was VFR with Unlimited visibility. Prior to flight; MX had informed us that the aileron disconnect light was worked on. They manually disengaged and reengaged the disconnection device to trouble shoot the cause of the aileron light being on. They believed it was a micro switch giving a false indication. We received the aircraft for our flight with the Aileron Disconnection light MEL'd and fueled for our 4.5 hour flight. Because of our heavy weight we asked for the Runway 14 which is the longer of the two runways. Before takeoff from runway 14 we performed our runway line up checklist which calls for a flight control check. After completing the checklist; I additionally asked the First Officer to try and move his yolk left and right as I held mine in place. This was to comply with the MEL's Operational Procedure. On the takeoff roll nothing felt different. On rotation or there after I felt the disconnection device disconnect and the artificial feel on the yolk went away. The aircraft was fully controllable and operational. I asked Departure that we would like to stop our climb and diagnose the problem. We noticed the yolks were disconnected then we ran the un-commanded aileron or elevator disconnection QRH procedure in the Non Annunciated section of the QRH. This simply had us pull the Affected Disconnection handle. Since we had just departed we were heavy with fuel and needed to burn off some so we could make landing weight. We held until we could make landing weight and returned and landed uneventfully.


Second narrative: Upon rotation the ailerons disconnected making them separate. Prior to departure we did control check as required by check list and MEL. All controls were correct and proper prior to departure. After rotation the PIC advised me the controls had disconnected; we then checked that both sides had control but separate. We were well above landing weight so we held for a while to burn sufficient fuel to make landing weight. We landed uneventfully.


Synopsis: EMB135 flight crew reported the ailerons spontaneously disconnected on climb out resulting in a return to the departure airport.
Date: 202011
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Aircraft component: Navigational Equipment and Processing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Workload
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Radar jamming resulting in loss of both transponders and GNS1 and GNS2. [Caused by] Military Radar Jamming.




Synopsis: Dispatcher reported Military Radar Jamming.
Date: 201907
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: Turbulence
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Weather
Primary problem: Weather

Narrative: Turbulence report flight from ZZZ to ZZZ1. I informed the flight attendants I didn't want to take chance and for them to stay seated for the beginning of the fight. After leveling off 28;000 feet and looking ahead the flight looked smooth. I informed them they could get up and perform service. Approximately about ten minutes later ATC informed us of a small build up that was ahead. So we both looked and did not see it; other than a bunch of haze due to looking into the sun and some stratus clouds that looked like they were below us. We asked ATC for 30;000 feet due to what he said; then we turned the radar on and by the time this was done you could see it was straight ahead and building fast. ATC said we could make a right turn; so I started climbing and made a right turn; but it was growing quite rapidly so I turn the autopilot off to help try to avoid this small build up and we caught just the tops of the clouds. That's when we encountered moderate turbulence; so I contacted the flight attendants as soon as possible to get an evaluation of what their condition was. They informed me that two had fallen and hurt their legs and the cart had fallen on its side. I asked them if they needed medical assistance and if we needed to land to get medical assistance; they said no. I checked back with them every 15 minutes to make sure they were still OK. I asked again if they needed medical assistance they said no; that they were just going to rest for a few. I informed dispatch of the situation. Also prior to landing in I ZZZ1 contacted operations to inform the flight attendant supervisor on call to meet the aircraft at the gate.  Clouds were deceiving not normal that stratus clouds will have this type of outcome .99.9% of the time it's always a cumulus clouds.




Synopsis: Pilot reported moderate turbulence that caused injuries to flight attendants.
Date: 201912
Local time of day: 0601-1200
Location: ROA.Airport, VA
Flight conditions: VMC
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C ROA
ATC / advisory: TRACON ROA
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Second reporter function: Captain
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: On approach into ROA we had the airport in sight. We were cleared for the visual to runway 24. We backed up the visual with the RNAV approach. In visual conditions right past the FAF we got a GPWS alert. With all terrain in sight we leveled off and the alert stopped. We seemed to be on altitude and lateral path at the time of the alert. We continued the approach to a normal landing. We believed the cause to be the initial pitch down when we started descending at the FAF.


Second narrative: On approach in to Runway 24 in to ROA; we were cleared on the visual; and proceeded to descend with all terrain in sight. We were on slope turning to final and received a GPWS alert. We leveled off while maintaining visual with the terrain; then proceeded to descend on standard slope in to Runway 24.Although we were at 3;700 feet at HIBAN and on glidepath; we believe a initial descent pitch may have caused the GPWS to alert.


Synopsis: CRJ-200 flight crew reported an erroneous GPWS warning on final approach to ROA airport.
Date: 201906
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: RV-12
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: J3 Cub
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Air Traffic Control Fully Certified; Flight Crew Commercial; Flight Crew Instrument
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I had been doing pattern work on RWY XX for about 45 minutes. All radio calls were made for each phase of flight; including upwind. As I was doing my sweep for traffic on final; and announcing at the same time; as my scan moved from the right back to forward; I noticed Aircraft Y just below me on a straight in approach to RWY XX. I immediately pulled up and turned right. I continued the right turn back to final and saw Aircraft Y landing on RWY XX. No radio announcements were made by Aircraft Y. At the altitude I was above Aircraft Y; I did not feel like we would have hit at that time; but had I not been above him and not able to see him; we very well could have hit as we got closer to the runway.While not required to fly a standard pattern by entering the pattern level on the 45; I believe requiring this type of pattern entry would increase safety. Just flying straight in with no radio calls; and without any regard for traffic in the pattern creates a hazardous situation.




Synopsis: RV12 pilot reported an NMAC with another light aircraft in the pattern at an uncontrolled airport.