elihoole/asrs-aviation-reports huggingface dataset:
Date: 201708
Local time of day: 1201-1800
Location: NUW.TRACON, WA
Flight conditions: Marginal
Weather elements / visibility: Haze / Smoke; 3
Light: Daylight
Aircraft: RV-12
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Descent
Airspace: Class E NUW
ATC / advisory: TRACON NUW
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Was on a VFR flight plan flight using ATC services. I cruised at 7;500 feet for the flight and began my descent [as I approached my] destination. I was under control of Whidbey (NAS) Approach. I was outside their Class C; but under their control.I was descending at 500 FPM; later 600 FPM; when 500 would not take me down to pattern altitude prior to reaching [my destination]. My glass panel display shows the location of arriving at selected altitude. The weather was VFR; but in heavy smoke; no clouds. The vertical visibility was limited; maybe 3-5 miles slant range; horizontal visibility was unknown; but very poor. The airport AWOS was reporting 8 miles and clear skies.While descending through 4;100 feet; the Whidbey Controller told me to maintain VFR at or above 4;500. I told him I had already passed 4;500 and was approaching 4;000 feet. He didn't reply; so I advised I was climbing back up to 4;500 feet. At that point another Controller came on frequency (an instructor? NUW seems to have many ATC trainees). He advised me to 'descend immediately; there was an immediate traffic conflict with another aircraft at 4;000 feet.'I disconnected the autopilot; pulled the throttle and pushed the nose over. I then leveled off at about 2;500 feet and resumed navigating to the airport. Because of the poor visibility; the Controller asked that I 'remain with him'; (they normally terminate radar coverage about their Class C boundary) and gave me radar vectors to the airport. I became visual with a landmark and was able to track it until I spotted the airport and entered a left crosswind for Runway XX. I then cancelled radar services and landed normally.On analysis of my data downloaded after the flight; I found I had pitched 20 degrees nose down; reached over 4;000 FPM rate of descent; and hit 145 knots IAS; 158 knots TAS (Vne for my airplane is 136 knots TAS.) The vertical acceleration went from +1.0 to +0.5 to +1.5 over a 7 second period. It had been running in the range of +0.8 to +1.1




Synopsis: The pilot of a VANS RV reported that ATC alerted him to an immediate traffic conflict with another aircraft.
Date: 201708
Local time of day: 1201-1800
Location: F11.TRACON, FL
Flight conditions: Mixed
Weather elements / visibility: Thunderstorm
Light: Daylight
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 129
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B MCO
ATC / advisory: TRACON F11
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Weather; Airspace Structure; Human Factors; Staffing; Procedure
Primary problem: Weather

Narrative: Aircraft Y was being worked by the STN controller on a 160 heading and clipped the corner of my airspace on final (ARM sector); right where Aircraft X was descending out of 6;000 for 4;000. Aircraft Y entered my airspace without a point-out. The STN controller was busy and had several areas of thunderstorms affecting his airspace. Aircraft Y passed less than 5 miles behind Aircraft X; a heavy with 700 feet of altitude. There was several significant areas of precipitation affecting the entire airspace and every sector was overwhelmed including the supervisors. There was not enough staffing to staff hand-off positions and coordinator positions. Supervisors were having to work Coordinator positions for the MCO departure sectors and arrivals sectors and were not able to keep an eye on other sectors than may need attention.I recommend adequate staffing levels to staff coordinator and hand-off positions so that supervisors are not having to stand behind just 1 sector to coordinate for an extended period of time and they can keep an eye on the entire operation. It is a known issue that F11 experiences significant thunderstorms every afternoon during the summer months and staffing was decreased instead of increased to allow for necessary positions to be staffed.




Synopsis: Orlando TRACON Controller reported an airspace incursion and a loss of separation due to another Controller being overwhelmed with traffic and weather.
Date: 202101
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch; Person Other Person
When detected: Other Takeoff Position
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Gate; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X had been blocked out for 12 mins at the time when they received an ACARS from load planning stating that 'Captain we have a ramp loading error with DG and need you to return to the gate. Zooming in on ZZZ in [Software] I could see Aircraft X was taking the runway. I immediately called the tower and asked them to tell him to come back to the gate as well as copy and pasted the message from load planning to him in another ACARS message. At that point it seemed like he had got the message and turned off the runway. The Load Planner also called me to inform me of the situation but at this point the plane had already turned off the runway. The issue is not load planning; the issue is ramp. This was a ramp directed loading flight and load planners didn't receive the information until it was almost too late. If the crew missed the ACARS or maybe if it were to have been rejected; they could have been airborne with the DG loaded improperly. Not only is this incredibly dangerous but happens entirely too often."




Synopsis: Air Carrier Load Planner reported notifying flight crew to return to departure gated due to a DG load configuration error detected as aircraft about to takeoff
Date: 201410
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Windshear; 10
Light: Daylight
Aircraft: Cheetah; Tiger; Traveler AA5 Series
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Nose Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Student
Human factors: Training / Qualification
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Human Factors; Aircraft; Weather
Primary problem: Human Factors

Narrative: I took off from ZZZ Airport after 3 successful patterns including 3 takeoffs and 3 landings at ZZZ; then I flew in the area within 25 miles for about 30 minutes and then landed at ZZZ1 Airport; took off from ZZZ1 and arrived back at ZZZ. Everything looked fine; but upon landing on Runway X; I was about 2 feet above ground and gusting wind suddenly blew me off the runway to the left. I applied power to do a go-around but did not help; the airplane landed on the grass and rolled. The nose wheel hit something and broke off and the nose and propeller hit the ground.




Synopsis: A student pilot experienced gusty winds during landing; causing a runway excursion with damage to the nose gear and propeller.
Date: 202012
Local time of day: 1801-2400
Location: LIT.TRACON, AR
Aircraft: Hercules (C-130)/L100/382
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Other Holding Pattern
Airspace: Class E ZME
ATC / advisory: TRACON LIT
Reporter organization: Government
Reporter function: Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While working Radar West a C-130 came off of LRF requesting direct to HERCK intersection to hold. I misread the approach plate with the holding procedures and issued an altitude of 2000'. The hold at HERCK is depicted at 3000'. The aircraft entered a 2200' MVA while holding at 2000'. I noticed the MVA as they entered it and immediately climbed them to 2200'.




Synopsis: Controller reported issuing a holding altitude below the minimum vectoring altitude: once realized; a new and higher altitude was issued.
Date: 201706
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Thunderstorm; Turbulence; 5
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: As I was coming in to land; there was a thunderstorm reported in the vicinity of the airport. There was pick gust of 20 knots reported at 090 degree. I managed to put the plane on the runway but the wind kept pushing me to the left of the runway and ended up in the grass field where I knocked off a couple of runway lights.




Synopsis: C172 pilot reported a loss of control after landing due to crosswinds that resulted in contacting runway lights and a runway excursion.
Date: 202010
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: Commercial Fixed Wing
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; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Distraction; Workload
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Approximately 3 hours into flight a group of 3 passengers would not comply with the Flight Attendant instructions regarding wearing their face masks.  She notified us and we told Dispatch of the situation and their seat location.  Shortly after; they became belligerent to the flight attendants and continued [with] non-compliance.  Now they were using foul language and disrupting other passengers.  The Captain asked one of the foreign language speaking flight attendants to go try and deescalate the situation but that only made things worse.  We looked in the Flight Operations manual and technically this was a threat level 1.  We discussed whether should we notify Dispatch and we agreed by the definition it was; but we did not really think this was anything other than a couple of intoxicated passengers.  The Captain got on the PA and addressed the cabin of the importance of wearing the mask.  After this announcement we had no further trouble with these passengers. They apologized to the Flight Attendant as they exited the plane in ZZZ.Mask requirements in cabin; possible intoxication; lack of respect for airline rules. As soon as the Captain made the announcement this problem went away.  Maybe we should have tried that sooner.




Synopsis: Air Carrier First Officer reported 3 passengers would not comply with the face mask policy during flight and became belligerent toward the flight attendants.
Date: 202103
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B737 MAX Series Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Aircraft component: Headset
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I flew the 737 Max aircraft for the first time and noticed an aircraft characteristic that I do not like. The altitude alerting system gives a loud buzz in the headset 900 ft. prior to level off MCP altitude. This buzz drowned out ATC communications twice during climbout due the timing of ATC communications. I was unable to determine what ATC was saying.




Synopsis: B737 MAX Captain reported noise on headset when using air/ground communications systems.
Date: 201911
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Situational Awareness; Troubleshooting; Time Pressure
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Equipment Problem Dissipated; Flight Crew Requested ATC Assistance / Clarification; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Environment - Non Weather Related; Aircraft; Airspace Structure
Primary problem: Environment - Non Weather Related

Narrative: Approximately 80 NM from the TLV FIR while in the Nicosia FIR; we lost our GPS. I believe it was because it was being jammed. We turned on 'Radio Updating' and advised ATC. Approaching the airport; we regained the use of the GPS system.  This is the second time my GPS has been jammed since the Ops Alert dealing with GPS jamming in the TLV FIR was rescinded.




Synopsis: B777 Captain reported possible GPS jamming.
Date: 201907
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: Thunderstorm
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Human Factors; Weather
Primary problem: Weather

Narrative: Departed on a 310 degree vector due to thunderstorms building west of the airport. Initially this vector was good and weather radar showed us just to the east of the heaviest convective activity/echoes. As we cleared the initial cumulonimbus and were switched to Departure Control we visually identified a building Towering Cumulus off of the nose of the aircraft on a 310 heading. This Towering Cumulus was not painting on radar but visually it was building and there was no doubt it would be turbulent. We immediately asked ATC for 10 degrees further to the east to avoid this build up. ATC advised something to the effect; 'It's not going to happen Company. I'm not authorizing deviations until I get a moderate report.' At this point we were close to entering the buildup. The cabin was secure so we honored ATC not knowing the traffic situation. As soon as we hit clouds; we experienced moderate turbulence and informed ATC. We were vectored immediately to the east cleared the weather. The flight continued uneventfully. Departure Control seemed to demonstrate a great deal of hubris while dealing with our request. Given that our radar did not depict a core; I'm sure that ground based radar did not depict a core. Given that the weather was building and we could visually see that a deviation would be warranted; I do not think ATC should be denying weather deviations. We could have declared an emergency and deviated; however that seemed extreme given what we were painting and the unknown consequence of deviating into arriving traffic. Generally; I think ATC should respect the firsthand knowledge of Flight Crew and prioritize safety rather than offering a rigid approach to a dynamic situation.




Synopsis: An Air Carrier pilot reported ATC refused their request for a weather deviation.
Date: 201906
Local time of day: 0601-1200
Location: ANC.Airport, AK
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class C ANC
ATC / advisory: TRACON A11
Reporter organization: Government
Reporter function: Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance
Contributing factors: Airspace Structure; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: Aircraft X was flying the KNIK2 SID out of ANC. The system initiated a Low Altitude notification. I issued a Low Altitude Alert to the pilot and advised an immediate left turn and climb. Recommendation: KNIK2 procedure change to include a DME arc not to penetrate during departure. This will give a finite point in space that is unable to be violated; and to preclude confusion about the SID wording by offering a hard boundary as a graphical depiction.




Synopsis: A11 TRACON Controller reported a low altitude notification for an aircraft flying the KNIK2 SID out of ANC airport.
Date: 201309
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Corporate
Operating under: Part 91
Flight plan: VFR
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class G ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Catastrophic engine failure in cruise. Landed on highway. No injuries. Aircraft may have sustained damage to landing gear due to hard landing. No damage or property losses to persons or property on the ground. Highway blocked or partially blocked for approximately 3 hours. Emergency services from Sheriff and State Police requested. Report filed with Civil Air Patrol immediately after securing aircraft; and recovery initiated. Telephonic notification of FAA Lockheed Martin FSS immediately after securing aircraft. Conference call with unknown individuals from FAA and NTSB (believe five persons involved on call; individuals did not self identify) after Deputy Sheriff's arrived on scene. Upon request by LEO provided pilot license; current medical; and photo ID for inspection. Documents returned upon request. Aircraft towed at recommendation of law enforcement and State Department of Transportation emergency personnel on scene to off highway location two miles south of initial landing site.




Synopsis: C182 pilot experiences engine failure at 5;500 FT with an emergency landing on a state highway.