elihoole/asrs-aviation-reports huggingface dataset:
Date: 201309
Local time of day: 1201-1800
Location: ZDV.ARTCC, CO
Weather elements / visibility: Clouds; 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 A ZDV
ATC / advisory: Center ZDV
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Other / Unknown; Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Fuel Issue; Inflight Event / Encounter Weather / Turbulence
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; Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airport; Weather; Human Factors
Primary problem: Human Factors

Narrative: Originating from PTT we were direct VFR to destination. I landed at GGF for a break and to be topped off with fuel. The airport had no power therefore no avgas. It was unlimited ceiling and visibility with the front visible from the runway. We climbed to 10;500 FT for an hour or so and proceeded to climb over the rising cloud deck. When I broke through class alpha I knew I was caught on top. The Controller reminded me I had broke through; but to maintain clear of clouds I told him I needed to stay up. Turning around and heading back to GGF was not possible since I only had 2.5 hours of fuel left and was 2.5 hours away from a VFR airport without a ceiling. I chose to continue northbound. The Controller was super helpful by talking me through the cloud deck; 9;000-5;000 FT. Once below the deck I landed. The problem arose;1. Lack of fuel to turn back caused by power outage at airport.2. Not IFR rated.Contributing factors.1. Several cloud layers and being boxed in at a rapid rate. Corrective actions.1. Complete IFR rating.2. Make decisions to turn back earlier. Center was a great help.




Synopsis: PA28 pilot reports being unable to obtain fuel at a planned fuel stop and electing to continue VFR over approaching frontal weather. Class A airspace is entered avoiding clouds which are noticed by ATC. ATC provides assistance to the private pilot to descend in IMC to 5;000 FT for a visual approach at a suitable airport.
Date: 201812
Local time of day: 0601-1200
Location: TTA.Airport, NC
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class G TTA
ATC / advisory: CTAF TTA
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Other / Unknown
Anomaly: Inflight Event / Encounter Bird / Animal
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: I conducted a recreational sightseeing flight over Jordan Lake. During this flight I noted that the presence of waterfowl and other birds had increased in the area. Prior to and again during the flight I noted that no wildlife/waterfowl preservation zones were noted in this area. Due to what may be a seasonal or migration change in the wildlife population; a notation on the sectional charts or a NOTAM may be beneficial to both the other pilots and the migrating wildlife.




Synopsis: Small aircraft pilot reported that after flying over the aforementioned area; a NOTAM and / or chart notation regarding the bird migration should be issued.
Date: 201903
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: B777-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Work Refused
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Lithium batteries pose a significant threat to passenger aircraft. The DOT has made it clear of the dangers associated with this material. Certain lithium items are exempt from the ban; those items carried in or with 'equipment; up to 5 kgs 11 lbs. Apparently there is no limit as to how many equipment items are allowed. This flight was scheduled to have 20 kgs of lithium aboard. The way the cargo and loaders throw these items around are a real concern. I've witnessed boxes being loaded up-side down and 'cans' being dropped off of loading equipment. I refused this load and believe that all lithium items as 'cargo' should only be transported on cargo only aircraft. [Company] is rolling the dice for the sake of profit by excepting lithium material packed in or with equipment. Remove all lithium items carried as cargo from passenger aircraft.




Synopsis: B777 Captain reported refusal of Hazmat cargo due to safety concerns regarding the handling of Lithium Ion batteries by ground personnel.
Date: 201706
Local time of day: 1201-1800
Location: TEB.Airport, NJ
Flight conditions: IMC
Weather elements / visibility: Fog; Haze / Smoke; Rain; 2
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B NYC
ATC / advisory: Tower TEB
Reporter organization: Air Taxi
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Engineer
Human factors: Situational Awareness; Training / Qualification
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Undershoot; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: Cleared for the ILS to Runway 6. Intercepted the LOC and GS (Glideslope). Crossed DANDY at around 1700. DANDY has a mandatory altitude of 1500. If you are on the GS you will cross DANDY slightly above 1500. Weather was marginal and focus was on the approach and remaining on the LOC and GS. Altitude deviation was not intentional. This mandatory altitude at DANDY needs to be removed or changed to meet the GS altitude.




Synopsis: CE560XL Captain reported becoming distracted after capturing a false localizer signal during the ILS Runway 06 at TEB. The mandatory crossing altitude of 1500 ft at DANDY was forgotten and the fix was crossed at 1700 ft.
Date: 201702
Local time of day: 1201-1800
Location: EGLL.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
ATC / advisory: Tower EGLL
Second aircraft: B747-400
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Two and a half minutes after a B747 was cleared for takeoff; we were cleared for takeoff on 9R at EGLL. We were cleared to LON 2.0 DME; then right heading 220 to climb and maintain 6000 ft. After takeoff; we were cleared to continue right turn to 250. At 2100 ft MSL; we encountered the wake of the preceding B747-400. It was 'moderate' by the coffee spill criteria and short-lived (3 seconds). It was only one encounter. It was while we were in 25 degree right bank and we probably got additional 10 degree right/left/right with associated yawing and some pitch (+/-5 degree?); airspeed probably +/- 10 KIAS (from 200 KIAS and accelerating during flap retraction). Nevertheless; it was a 'little wake; huh' type of encounter that was mitigated by everyone being in seat belts and down (flight attendants). Winds on surface were east at 10-15 knots. My guess is that the B747 flew a wider turn. It was definitely smooth until the encounter and smooth afterwards (not much; if any; ambient turbulence). I am not sure what winds were at 2000 ft. We reported the wake encounter to tower controller before we were handed off to next frequency (about 2700 ft MSL).




Synopsis: B767 First Officer reported encountering wake turbulence on departure from EGLL in trail of a B747.
Date: 201604
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: M-20 J (201) / Allegro
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear Tire
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Private
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Left main landing gear tire blown on landing with [ATIS] information - Winds 060 at 10; VIS 10SM; Clouds FEW at 25; SCT at 35; BKN at 55; Altimeter 30.15; RWY 3 and 35 in useI landed on RWY 03 center line; and the rear wheels touched down at approximately 50-60 KIAS with very little impact felt. As the nose lowered the plane felt loose on the ground and skid to the right approximately 3 degrees. I countered the right skid with a left pedal and right aileron as the nose came down. The plane then skid hard to the left roughly 15 degrees. I applied right pedal with right aileron to oppose the left skid; and the aircraft continued veering towards the left side of RWY 03. As the wing tip neared the side marker lights I applied right brake with full right pedal and continued to apply right brake pressure until the severity of the left turn was only a few degrees. The plane became more controllable as it slowed to the speed of a brisk walk. This allowed a small amount of directional control to the right keeping the aircraft on the runway; also avoiding contact with runway lighting. No bodily injury or property damage occurred from this event.




Synopsis: The pilot of a M20J reported control problems on landing rollout due to a failed tire on the left main landing gear.
Date: 202009
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Weather elements / visibility: Haze / Smoke; 3
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Time Pressure; Communication Breakdown; Distraction; Troubleshooting; Workload; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Human Factors; Environment - Non Weather Related; Staffing
Primary problem: Staffing

Narrative: On a recent IFR flight from ZZZ1 to ZZZ we encountered very poor service from Approach Control facility.  We were descending from FL380 anticipating radar vectors for the ILS Runway XXL at ZZZ.  We were handed over to Approach from Center and experienced a challenging time trying to establish and maintain VHF communications with Approach.  We had to request a descent numerous times during the arrival phase of our flight.  Approach was managing a huge area of airspace with numerous aircraft and firefighting aircraft all trying to accomplish their particular mission.  By the time I arrived at ZZZZZ Intersection of the ILS approach to Runway XXL at ZZZ I was still at 8;000 feet MSL and still trying to continue the descent.  The Controller was just too busy to accommodate or even acknowledge our requests for descent.  Since the advent of the COVID virus service from ATC has not been very good.  I'm not trying to place blame on any individual controllers rather I'm trying to highlight the need for more ATC Staff.  Operating shorthanded is dangerous.  Please make it known that our air traffic control system is currently hobbled and I don't feel confident with their service right now.




Synopsis: Pilot reported ATC being too busy to communicate with them while attempting to request a clearance to descend.
Date: 202004
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Windshear; 10
Light: Daylight
Aircraft: Cessna 150
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Private; Flight Crew Instrument
Human factors: Human-Machine Interface; Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Ground Strike - Aircraft; Ground Excursion Runway; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: During landing after a pattern flight and clearance for options; I approached final to land on Runway XXR; the airspeed; decent rate; power and flaps all set properly. Airspeed on final 55kt; full flaps deployed; Just before the flare; suddenly the airplane hit runway hard and bounced off. I attempted a go around but aircraft quickly stalled again and hit the ground hard again. The nose gear collapsed; prop struck pavement and came to stop. There were no personal injuries sustained. I informed the tower; I was ok and came out of the plane. I was able to move the plane off runway with the help of another person who showed up a few minutes later. I called the tower after securing the plane as advised.  I cannot think of any reason; other than a possible wind shear. However ATIS reported wind 310 @ 11knots without any mention of wind shear. If possible at all; improved monitoring for wind shear could be considered to prevent similar incidents in future.




Synopsis: C-150 pilot reported loss of aircraft control on landing resulting in a hard landing and causing the nose gear to collapse.
Date: 202005
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Light Transport
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter function: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Enroute; we were cruising at 14;000 feet awaiting a climb (planned FL340). My FO and I heard us cleared to FL270 from Center. My FO read the climb clearance back without comment from ATC. We began a climb and sometime just above 16;000 feet; ATC came on frequency with instructions to descend; that we were not cleared to climb. We immediately began a descent. I apologized and explained what we heard and read back. ATC did not respond. Remainder of interaction with Controller was uneventful; as was the remainder of the flight.With the pandemic; prior discussions with ATC informed me that less traffic volume has resulted in Controllers covering more simultaneous sectors. I'm wondering if the climb clearance was given to an aircraft on a different frequency (with a similar call sign) such that we heard no other aircraft read back the clearance; further reinforcing our belief that the clearance was for us. My FO and I discussed the event and still believed that our tail number received the clearance.




Synopsis: Pilot reported a communication issue resulted in an altitude deviation.
Date: 202007
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction; Workload
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors; Staffing
Primary problem: Staffing

Narrative: I'm working LC-X Runway XXR; XXL (closed); XY. Arrivals to Runway XXR only. At some point I was told I would be getting departures and a normal split (meaning I would be departing all south and east bound departures). This seemed like a bad idea as they were light departures for YYL; the departure only that doesn't ever have to be crossed. This next part is not operationally significant but relevant. Because of the fear of COVID-19 I responsibly self distance and work as far from anyone else as I can. I moved to work from the LC-XX position to lessen my distraction for fear of infection and as this was about to get complex I needed to. I was then instructed to depart and arrive Runway XXR at this time there are no longer any departures for YYL the departure only Runway. The space between my Runway XXR arrivals is too small to get but one departure out. I told my departing aircraft to expect a 10 minute delay (ended up being 18 minutes.) I felt pressure to depart in the small gaps to try to save this mistake however it simply couldn't be done without having a plethora of deals. In addition working the position from LC-XX was a different prospective then I'm used to working LC-X from and didn't make this any easier even though moving to LC-XX was my decision.These are strange times no doubt and complexity to operations because of the Coronavirus is just going to be a new thing that reporting is going to get whether its your responsibility to hear such complaints or not. As the airlines attempt to increase operations more positions will have to be opened and it's our mission to put the operation first but we shouldn't open them just because you don't want to have to many people on break.Short answer: Runway YYL should have remained the only departure Runway.




Synopsis: Tower Controller reported a 'plethora of deals' due to working with small arrival holes and not using the designated departure runway.
Date: 201509
Local time of day: 0001-0600
Location: PVD.TRACON, RI
Aircraft: Citation Excel (C560XL)
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Flight phase: Cruise
Airspace: Class E PVD
ATC / advisory: TRACON PVD
Reporter organization: Fractional
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: While over UUU airport at 2;000 feet and 200 knots we were on a heading of 090 degrees assigned by PVD departure. I was the pilot flying and visually saw 2 parachutes; with jumpers attached. We were approximately less than half a mile from them. Same altitude as our aircraft. We were basically coming head on. I disconnected the autopilot and took an evasive right hand turn to avoid the jumpers. We asked PVD about jumping in the area over UUU airport and they said they did not have any info about jumping over that airport. We asked the next PVD controller and were told the same thing. There were no NOTAMs about jumpers over UUU. When we landed I called the airport manager. He spoke with the jump plane and he said that the jump plane was talking to PVD and that PVD had even warned the jump plane about us!!! We were never warned or told by PVD of any jumpers nearby.PVD Departure was either confused or did not tell us. We had a near miss with jumpers and it was too close. Better ATC communications would be much safer.


Second narrative: PIC spotted skydivers under canopy directly in our flight path; and it took significant aggressive maneuvers to avoid impact. (Approximately 50 degree bank and 30-40 degree course change).


Synopsis: CE-560XL flight crew reported they had to 'aggressively maneuver' to avoid a midair collision with unreported skydivers in the vicinity of UUU airport.
Date: 201910
Flight conditions: VMC
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
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: Situational Awareness; Training / Qualification
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Had to stop abruptly while taxiing in to [gate]. Caught a white van out the corner of my left eye coming from the left and not slowing down. I think the Marshaller caught it about the same time. He kept cruising and appeared to pass under the nose [of our aircraft]. First Officer said it appeared as though the driver was texting. I have no doubt that he or she probably was; and I would love to see the video if I could.




Synopsis: B767 Captain reported a near miss with a ground vehicle that did not yield to the aircraft.