elihoole/asrs-aviation-reports huggingface dataset:
Date: 201207
Local time of day: 1201-1800
Location: SFB.Airport, FL
Aircraft: SR20
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Flight phase: Final Approach
Airspace: Class C SFB
ATC / advisory: Tower SFB
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
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: An SR22 was inbound from the south on a modified right base entry; requesting pattern work. Aircraft was at 1;500 FT; was given the instruction to descend to pattern altitude at pilot's discretion; and to enter the right base to Runway 09R. Additional traffic was to this aircraft's left; making a base entry to Runway 09C for a full stop. Additional traffic was already established in the right traffic pattern of Runway 09R. I misjudged the timing of the inbound the SR22 with the other aircraft in the pattern. My plan was to have the SR22 be first to the runway; and the established aircraft follow the SR22. It ended up being a tie; and I tried to correct the situation by having the SR22 fly eastbound (opposite direction of the other aircraft) with the attempts of having the SR22 now follow the other aircraft. I issued traffic to the SR22 after I told him to make the eastbound turn. The pilot did so; and came close to the other aircraft. There are many things: keep the inbound aircraft at 1;500 FT altitude; could have had existing aircraft make a left 360 in the downwind to create more spacing; could have extended the existing aircraft's upwind; could have turned the SR22 westbound; could have had more urgency with the pilot to have him execute his eastbound turn immediately and give a traffic alert to advise him of the reason for the immediate turn.




Synopsis: SFB Controller described a pattern conflict resulting from ATC spacing misjudgments.
Date: 202109
Local time of day: 1801-2400
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown; Confusion; Communication Breakdown; Time Pressure; Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I went off of comm one briefly to call ramp.  We were approaching taxiway 1 for the ramp and parking. I got cleared in from ramp.  I turned my head up and left and saw Aircraft Y that seemed to fill the entire windshield. The Captain was already starting to brake and I added additional braking from my side because he was so close. I told ground we almost hit Aircraft Y. Ground said sorry.  Aircraft Y said ground told him we would give way.  I never heard that clearance or acknowledged it.  Aircraft Y was taxiing fast down taxiway 1. Was not stopping for anything obviously.


Second narrative: Landed at ZZZ; taxi instructions taxiway 3; 2; 1 to enter ramp for gate.Making the left turn from 2 onto 1; had to slam on the breaks to avoid a collision with Aircraft Y traveling at a high rate of speed southbound on taxiway 1. Asked ground what happened and they said 'sorry' while Aircraft Y stated that we were supposed to give way to them.We did not hear or acknowledge any such instructions. Continued the taxi to gate.


Synopsis: Air Carrier Pilots reported a critical ground conflict during taxi to their ramp/gate. The pilots were forced to initiate an abrupt stop just prior to entering a taxiway. Another aircraft; was proceeding down the taxiway and was not going to yield. The pilots reported they did not hear any instructions or acknowledge to yield for the other aircraft.
Date: 201404
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-32 Cherokee Six/Lance/Saratoga/6X
Operator: Personal
Operating under: Part 91
Flight plan: None
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 Instrument
Human factors: Confusion
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: Taxi
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I landed and had a flat right main tire.  I was unable to exit the runway.  It took approximately 1 hour to clear the runway. The issue is that when speaking to the FAA inspector he asked for my registration.  I explained that I have been waiting for the FAA to send it; but they are backed up.  It has been a very frustrating experience.  The pink form 8050-1 states; 'Pending receipt of the Certificate of Aircraft Registration; the aircraft may be operated for a period not in excess of 90 days; during which time the PINK copy of this application must be carried in the aircraft.'  Upon advice of the inspector; I called FAA and they explained that I should not have been operating the aircraft.  That section does not apply.  I have not gotten an explanation why if the form says I can operate then why can I not?  This is very confusing and it is exacerbated by the difficult process of getting my registration. If I operated the aircraft when I shouldn't have then the PINK form needs to be changed.  I don't think there is any interpretation other than the one that the form states very clearly.  I truly believed that I was operating legally.  My mechanic is changing the tire tomorrow and he might have an explanation for the blown tube.  I don't know if I ran over anything on takeoff or on the landing.




Synopsis: After landing with a flat tire; a PA-32 pilot is informed that his temporary registration may not be valid although the 8051-1 clearly states that the aircraft may be operated up to 90 days with the pink copy.
Date: 201311
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Second aircraft: Challenger CL600
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings; Procedure
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Aircraft X was climbing to his requested altitude. Aircraft Y was underneath and in front of Aircraft X. Due to westbound traffic; and not wanting to delay Aircraft Y at FL270 for 60 miles; I decided to stop the climb of Aircraft X at FL270; and climb Aircraft Y through Aircraft X. Aircraft Y was out climbing Aircraft X 4:1 at one point. There was a 60-ish knot overtake the entire time; with Aircraft X behind Aircraft Y; however it was a controlled and calculated overtake and climb. I calculated the closure rate; the climb rate of Aircraft Y; put a 'J-Ring' on Aircraft Y; and decided there was no risk involved with this maneuver. Apparently; my calculation was 8 seconds off. The loss of separation occurred. This is the first operational error of my career. There was no traffic complexity or volume in the sector. I had nothing to watch except this situation; and that's what I was watching. Not once did I observe the target of Aircraft X go inside of the 'J-Ring' on Aircraft Y. Had I thought my calculations were incorrect and this was going to be a loss of separation; it was incredibly easy to fix; using turns; stopping an aircraft's climb; etc. It was well calculated and was not going to be an issue. The fact that I was apparently 8 seconds off (2/3 of a single RADAR sweep) in my calculation could be attributed to any number of factors; including a late report by the pilot; right down to the acceptable margin of error for the RADAR mosaic resolution; especially considering multiple RADAR Sort Boxes were in play. The lateral separation was reported to me as 4.96 NM...or less than 50 feet horizontally. If someone can actually prove to me that the aircraft were 49 feet off of those 5 miles; I'll eat my shoe. Like I said; I monitored the entire situation almost exclusively and not once did I observe the target inside the 'bubble'. A move to ADS-B/NEXGEN RADAR so we can actually get accurate position resolution.




Synopsis: Enroute Controller experienced a loss of separation detected by automation; the reported estimating the separation loss at less than fifty feet.
Date: 201604
Local time of day: 1201-1800
Location: ZAU.ARTCC, IL
Light: Daylight
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZAU
ATC / advisory: Center ZAU
Second aircraft: PC-12
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter

Narrative: Aircraft X was on the arrival and level at 15;000 feet. Aircraft Y was stopped short at 14;000 feet. The Aircraft Y passed 5-6 miles behind Aircraft X and reported severe turbulence; determined to be wake turbulence.[We need] better awareness of wake turbulence.




Synopsis: An aircraft reported severe wake turbulence.
Date: 202102
Local time of day: 1201-1800
Location: GMU.Airport, SC
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class D GMU
ATC / advisory: Tower GMU
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Student
Human factors: Communication Breakdown
Anomaly: Conflict NMAC
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I was performing touch-and-go's during a supervised solo flight. On my final approach (GMU Runway 19); the other aircraft; who was told by ATC to continue flying through the final; took a northbound turn straight in front of me; flying directly towards me. I took evasive maneuvers by dropping down to the right. The other plane; only after being told by ATC that he had cut someone's final off; also took evasive maneuvers and started flying to his right and upwards. Following the evasive maneuver; landing on Runway 19 was uneventful.




Synopsis: Student pilot reported a Near Mid Air Collision on final approach with another aircraft  that required reporter to take evasive action.
Date: 201206
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: DVFR
Mission: Personal
Flight phase: Cruise
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Made an emergency landing at [a military field] due to engine misfiring.




Synopsis: C172 pilot reports landing at a military field due to a rough running engine.
Date: 202007
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Airspace: Class B ZZZ
Aircraft component: Cargo Door
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Time Pressure; Workload; Troubleshooting
Second reporter function: Technician
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Incorrect / Not Installed / Unavailable Part; Procedure
Primary problem: Procedure

Narrative: I failed to control the situation correctly. This is my error only. I should have stopped Aircraft X when I was told that there was a roller possibly missing from the cargo door support on the rail. The door was reinstalled to the rail and allowed to continue. We are not allowed to fly with missing parts. I hesitated at the time but erroneously called this a non event and allowed Aircraft X to continue to ZZZ1 flight. This was my error.


Second narrative: We took a call from Company Maintenance stating the cargo door stuck when the ramp. Agents tried to close it. I went to Aircraft X to find the door was off its track on both sides and the aft upper track roller was missing; just the wheel axle was present. I re-seated the door on its track and was able to close and lock the door for flight.  I called Maintenance Control and informed [them] of the missing track wheel and if [they] wanted to place it on MEL or clear the item; Maintenance Control informed me that there is no MEL/CDL relief for this specific item and told me to sign the Corrective Action and [complete the appropriate paperwork]; putting the aircraft back into service as serviceable.   Aircraft was then released for service and flew from ZZZ to ZZZ1 with 49 souls onboard.


Synopsis: Technician reported allowing aircraft to fly with parts missing on cargo door.
Date: 202010
Local time of day: 0601-1200
Location: F70.Airport, CA
Flight conditions: VMC
Aircraft: No Aircraft
Reporter organization: FBO
Reporter function: Other / Unknown
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Anomaly: Conflict Airborne Conflict; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: It is my responsibility to alert pilots of a growing concern at the F70 (French Valley) uncontrolled airfield.  In the past 6 months there have been 8 traffic conflicts (evasive maneuvers taken); 3 Near Mid Air Collisions; and 6 unsafe (not in compliance with FAA rules and regulations) traffic pattern operations. As this airfield continues to grow in popularity and activity there is an increasing desire and need to have this airfield added to the Contract Tower list for controlled airspace.




Synopsis: Reporter stated there are multiple traffic conflicts and near mid air collisions reported at F70 uncontrolled airport.
Date: 202105
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Weather elements / visibility: Cloudy; Icing
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pitot/Static Ice System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Weather; Aircraft
Primary problem: Weather

Narrative: Started descent for the ZZZZ 1 arrival into ZZZ from FL400.  At approximately FL330 we received an IAS DISAGREE message. I checked all 3 airspeed indicators and mine matched the standby while the Captain's showed 10 KTS slow. Captain ran the appropriate checklists. Shortly after finishing the checklist we got an ENG master caution. I looked up and saw the Electronic Engine Control (EEC) had both reverted to ALTN. Captain ran the checklist. At approximately FL200 we got the ALT DISAGREE message; again ran the checklist. As we descended the Captain's airspeed indicator got as low as 40 KTS slower than my airspeed indicator and the standby airspeed indicator.  We continued to descend via the arrival and shot the visual approach to Runway XXL with no other issues or incidents.




Synopsis: B737 First Officer reported an airspeed split and Electronic Engine Controls both switching to alternate while in icing conditions.
Date: 201310
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Emergency Light
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At cruise over ZZZ; Flight Attendant called to say lights in both aft lavs were flickering; [and] then went out. Emergency Exit light in aft lav was only light on; and too hot to touch. I passed information to Maintenance Controller and he suggested pulling Circuit Breaker (C/B) H7 on Captain's overhead panel that controls the three Emergency lights in three lavatories. I pulled C/B and had Flight Attendant check; hot light went out. All other operations normal; continued to destination. Maintenance Control suspected light batting [insulation].

Callback: Reporter stated the aft Flight Attendant called him after she started noticing an odor that smelled like overheated; melting plastic coming from one of the aft lavatory light fixtures on an A320 aircraft. Concerns about potential cabin smoke or fire developing could have been a greater issue if pulling the Circuit Breakers (C/B) for the aft lavatories Emergency Lights had not shut the lights off and stopped the odor.



Synopsis: Captain on an A320 aircraft reports the aft Flight Attendant informed him of an odor that smelled like overheated; melting plastic coming from one of the Emergency light fixtures in the aft lavatory.
Date: 201701
Local time of day: 0001-0600
Location: KZAK.ARTCC, HI
Flight conditions: VMC
Light: Night
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A KZAK
ATC / advisory: Center KZAK
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Procedure; Weather
Primary problem: Weather

Narrative: Enroute [while over the Pacific Ocean] I was notified by ATC and Dispatch of a SIGMET that had a report of Observed Severe Turbulence on our route and altitude. I attempted for one hour to get a new route north of the area or lower altitude below the reported/forecast area of turbulence. Approaching fix GITLE after ATC was only willing to let me offset 50 NM south into the forecast area to get a lower altitude and Dispatch was unable to get ATC to change my route; I [exercised my Captain's authority]. We turned 45 degrees north and offset 15 NM then descended to FL270. Then we returned to our route. FL270 was below the SIGMET area. I prepped the cabin for turbulence while we passed the area just in case. The flight was normal and ATC and Dispatch were advised.




Synopsis: B737 Captain reported deviating around an area of reported severe turbulence on a trans-Pacific flight without ATC approval.