elihoole/asrs-aviation-reports huggingface dataset:
Date: 201710
Local time of day: 1201-1800
Location: SLC.Tower, UT
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B SLC
ATC / advisory: Tower SLC
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Distraction; Workload; Time Pressure; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight; Taxi
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Airport; Company Policy; Procedure; Equipment / Tooling; Human Factors
Primary problem: Company Policy

Narrative: I was working local center south flow. RWY 16R was closed for rubber removal (It was supposed to be closed only at nights for several days; but the airport decided to close it all day for several days). There was also a taxiway closer on G; so all the aircraft waiting were on taxiway H with blocked any of the H12; H11 exits.It was one of our busier departure/arrival banks. Approach was giving us seed and spacing for both RWYS 16L/17. As local center I was catching arrivals; launching turn departures; crossing straight out departures to 17 and crossing arrivals. As the controller I felt pressure to get aircraft moving; since there was a line of aircraft on both sides of the runway waiting to cross and depart. Approach was giving about 5 mile holes with arriving aircraft on final.I put Aircraft X in position; and crossed three aircraft down field; with Aircraft Y on final. For some reason I crossed 2 aircraft at H10; and one at Q. I realized that I messed up by crossing two at H10; and that I did not have the spacing needed while scanning the runway for my take off clearance. I canceled Aircraft X and asked if he could exit the RWY at H12; he said unable so I sent Aircraft Y around.Asking for greater spacing from approach would have helped relieve some of the pressure/complexity for the local center controller. Skipping a hole to just cross aircraft would be wise. I also think that the airport could do some of its optional runway closers during less busier times of the day.




Synopsis: SLC Tower Controller reported runway and taxiway closures increased their workload causing them to have to issue an arriving aircraft go-around instructions.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Flight Instructor
Second reporter function: Pilot Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Loss of power in flight; precautionary landing in open field.Plane was purchased and a condition inspection was completed. A program letter was provided to FSDO and receipt was confirmed. Plane was run for an extended period of time and was being flown from ZZZ to ZZZ1. Engine operated normally for 1.5 hrs prior to issue. Engine started to lose power and small amounts of smoke were produced. The plane is a STOL plane and I elected to land in an open field instead of attempting to fly over a populated area toward the airport. There was no damage to the plane; and a normal landing was made. We requested priority handling with tower when we elected to land in grass. We were a flight of two.


Second narrative: I was lead pilot/plane in a flight of two from ZZZ to ZZZ1.I was in contact with approach as a flight of two. The other plane referred to as 'plane 2' in the flight had engine trouble and partial loss of power. I requested priority handling for the aircraft in distress. They elected to land in an open field with no damage to plane and no injuries.The [plane] that landed in the field is a short take off and landing aircraft and equipped to land in grass. A normal landing was made.I in 'plane 1' circled over head as requested by ATC to ensure the pilot evacuated the plane safely and to report location to ATC to relay to police/emergency response.ATC was contacted via telephone by the pilot in 'plane 2' after precautionary landing


Synopsis: Pilot reported engine power loss in cruise and elected to land in grass near the destination airport.
Date: 201403
Local time of day: 1801-2400
Location: N90.TRACON, NY
Flight conditions: VMC
Light: Dusk
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class E N90
ATC / advisory: TRACON N90
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Other / Unknown
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Contributing factors: Manuals; Procedure
Primary problem: Procedure

Narrative: They make us work staggered 22L/R final in VFR conditions and the airspace is such that all aircraft have to be descended below the Class B. A busy VFR airport lies below the base leg and I almost had a mid air with a VFR jet; 1200 code; climbing into an air carrier. Change the airspace; or Class B; or don't have us use this approach in VFR weather. There will be a mid air here if this continues.




Synopsis: N90 TRACON Controller states it is facility policy to descend below the Class Bravo which causes conflict with busy VFR airport airspace on base leg to major airport.
Date: 201712
Local time of day: 0001-0600
Location: CLT.TRACON, NC
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B CLT
ATC / advisory: TRACON CLT
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict Airborne Conflict; Inflight Event / Encounter Other / Unknown
Detector: Automation Aircraft RA; Automation Aircraft TA
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Company Policy
Primary problem: Company Policy

Narrative: I was climbing the SID to the assigned altitude of 8000 feet. At about 6500 feet; departure advised us descending traffic would level off at 9000 feet. The First Officer was hand flying. He didn't reduce power to reduce climb rate; so I simultaneously reduced some power and told him to reduce climb rate. While climb rate was reduced at 7000 feet; we were given an RA; which told us to level off. We leveled off at 7300 feet. I advised ATC we were responding to an RA and would be maintaining current altitude until clear of conflict. He said; advise when clear of conflict and climb to 8000 feet when able. The TCAS system quickly advised of the RA. I followed the instructions of the TCAS system.I believe all departures assigned an altitude of 8000 feet and most arrivals having an assigned altitude of 9000 feet are too close in proximity. There are many Traffic Alerts which don't result in RA's due to reducing climb rates. I believe these Traffic Alerts could easily be avoided by adjusting assigned altitudes to 2000 feet versus the current 1000 feet separation currently in use. For example; departures stopping at 7000 feet or stopping arrivals at 10000 feet which ever would be easier for ATC would keep a greater safety margin.




Synopsis: A pilot reported they had to respond to an RA for known traffic that was restricted above their assigned altitude.
Date: 202105
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Brake System
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I rented the Cessna 172; Aircraft X from FBO in ZZZ1 to ZZZ at XA:00 on Date. I did a checkout on the day before. Before takeoff; I followed the checklist to perform the pre-flight and everything was normal; both brakes worked fine.At around XB:10; Aircraft X entered the final leg for Runway XX on ZZZ with 240 at 9 knot wind. I did a short-field landing and touched down smoothly on the second white stripes after the number XX with power idling. After the touchdown; the aircraft was rolling on the runway. I pulled out the yoke and stepped on both pedals to slow down the aircraft. The aircraft slowed down a little bit when taxing near the first exit. However; the airplane was still rolling when it approached the second exit. I checked the pedals and found that the left pedal was lost with no response and the right pedal was OK. So I reached out my right foot to the left pedal on the passenger side to make sure if that one was working; but it was not. In the meantime; my hand turned the yoke to the left subconsciously because the taxiway was on the left of the runway. After I turned the yoke; I saw the aircraft was going left slightly so I decided to turn the yoke all the way down to the left and finally the aircraft turned 180 degrees to the left from the runway to the dirt road. The right-wing struck the fence causing damage when turning. I pulled out the parking brake and the nose turned to the right slightly and stopped. I saw the hydraulic fluid was leaking from the left side of the brake's leg after I got out of the aircraft.




Synopsis: C172 pilot reported left brake malfunctioned on landing roll out causing a runway excursion.
Date: 202102
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Cessna 152
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear Wheel
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Landed on the runway at ZZZ. Several seconds after touchdown I felt nose shaking followed by loss control of the nose wheel. Stopped on Runway XXR had operations determine I need a tow back to the FPO. Was towed back and no other damage to the aircraft




Synopsis: C-152 pilot reported a nose-wheel problem on landing roll-out.
Date: 201506
Local time of day: 0601-1200
Location: DIJ.Airport, ID
Flight conditions: VMC
Weather elements / visibility: Clear; 10
Light: Daylight
Aircraft: A-1 Husky
Operator: FBO
Operating under: Part 91
Flight plan: None
Flight phase: Landing
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Other / Unknown
Anomaly: Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
Result: Flight Crew Regained Aircraft Control
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: During landing after towing a glider in an Aviat Husky; after transition from wheel landing to tail wheel I lost directional control and performed a ground loop. Aircraft spun around between two taxi lights facing the runway. No damage to the aircraft was observed. After preflight operations presumed.




Synopsis: The pilot of an Aviat Husky lost control during landing; resulting in a ground loop with no damage reported.
Date: 201207
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Fractional
Operating under: Part 91
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [Shortly after] takeoff at about 300 FT AGL the ACM O'HEAT came on followed by the left BLD AIR O'HEAT. There was black acrid smoke in the cockpit and the cabin. Due to the fact we were in a critical phase of flight and at low altitude; we turned the pressure source to OFF and declared an emergency. We entered the downwind and configured for landing. The Captain briefed the passengers over the intercom. When we were abeam the numbers the smoke started to lessen. After landing we cleared at the first available taxi way; performed an emergency shut down. While the Captain performed the shutdown the First Officer evacuated the passengers. We gathered about 100 FT in front of the aircraft and let the Fire Department check the plane. There was no fire detected.


Second narrative: [Narrative 2 had no additional information.]


Synopsis: CE-560XL flight crew reported shortly after takeoff they had ACM O'HEAT and BLD AIR O'HEAT messages; as well as black smoke in the cockpit and cabin. They declared an emergency; returned to departure airport; and evacuated the aircraft.
Date: 202201
Local time of day: 1201-1800
Location: D01.TRACON, CO
Flight conditions: IMC
Weather elements / visibility: Rain
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B DEN
ATC / advisory: TRACON D01
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Time Pressure; Situational Awareness; Human-Machine Interface; Distraction; Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Software and Automation; Aircraft; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: On final approach in IMC; ILS 35L at DEN; XA:45 MST. After configuring the airplane for final approach; we had an alert message with associated Master Caution [warning]. The alert message was for NAV ADS-B RPTG 1 Fault. It came on and off several times. We complied with the QRH procedure and switched the Transponder to position 2. It failed several more times with a Master Caution. Several aircraft on approach were reporting the same issue and ATC said that had been hearing about it all day with no explanation.




Synopsis: Air Carrier First Officer reported on final approach to Runway 35L in DEN the Master Caution warning sounded for the loss of GPS and ADS-B. Informing DEN ATC; the pilots were told it had been occurring all day.
Date: 201908
Location: MYF.Airport, CA
Weather elements / visibility: 10
Light: Daylight
Aircraft: Commander 112A
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class B SAN; Class D MYF
ATC / advisory: TRACON SCT; Tower MYF
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was approximately 30 miles northeast of MYF at 10;500 ft. when I asked Approach Control to descend for the approach into MYF. I was advised to descend and maintain 7000 ft. I did so; and was expecting a lower altitude when I got closer to the airport. When I got closer and not receiving a lower altitude; I called back to Approach for lower altitude when I was about 5 miles from the airport; and the Controller cleared me down to 3500 ft. and to cross a road ahead and told me to contact the Tower.At this point I was to lose 3500 ft. in 2 miles or so. Normally I try and descend no more than 500 fpm; however I needed to descend 1000 ft. to 1200 ft. to get down. I contacted Tower and what I believe was cleared to land on Runway 28R which I confirmed.Looking at the runways; I noticed two aircraft waiting to take off on Runway 28L and one aircraft waiting to take off on Runway 28R. At this point I was at least 1/2 to 3/4 mile and approximately 1/4 mile northeast of the runway. All of a sudden; the Controller cleared the aircraft waiting to depart on Runway 28R for takeoff. I contacted the Controller for clarification on what runway I was cleared for and he told me to go around. My aircraft at this point would have been able to land on either runway; however; I went around and finally landed on Runway 28L. When I was taxiing in to the FBO; I was told to contact the Tower for a phone number to contact them; which I did. I asked the Controller what the situation was; he stated he was going to make a report not for a runway incursion; but for something else; can't remember what it was. I honestly believe I was cleared for Runway 28R since that was the closest one to me; and the Controller never corrected me when I confirmed that runway. I could have easily landed on Runway 28L if that was where he wanted me to land; but he said to go around.




Synopsis: Pilot reported confusing Air Traffic Control instructions during approach to land.
Date: 201402
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp ZZZ
Aircraft component: Flight Dynamics Navigation and Safety
Reporter organization: Air Carrier
Reporter function: First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: After push and starting Number 2 Engine; we were notified of late bags. [We] shutdown Number 2 Engine. After loading the bags and during the restart of Number 2 Engine; we noticed the CDS [Common Display System] fault light on my side. Captain had the ground crew remain on the headset in case we needed them and got out the QRH. We were cleared to start Number 1 [Engine]. I started Number 1 [Engine]. At some point; the light went out. I did not verify with the Captain what the QRH had as guidance after completing the start of Number 1 Engine. Upon landing and shutdown; the CDS fault illuminated on both sides. I looked in the QRH and found out it needed maintenance action. Logbook entry made and Captain contacted Maintenance. Discrepancy was created by Maintenance. We needed to affirmatively communicate we had the right procedure and what needed to be done.




Synopsis: B737-700 First Officer reports a CDS fault light while starting Number Two Engine; which the Captain is able to clear using the QRH while the Number One Engine is started by the First Officer. Upon arrival at destination the CDS fault illuminated on both sides and the QRH indicates that maintenance action is required.
Date: 201208
Location: ZZZ.ARTCC, US
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Pressurization alarm sounded. Emergency descent accomplished. Held at 10;000 FT to burn down weight.

Callback: Reporter indicated aircraft type was B757-200.



Synopsis: B757-200 First Officer reported loss of pressurization at FL350. Emergency descent was executed.