elihoole/asrs-aviation-reports huggingface dataset:
Date: 201507
Location: ZLA.ARTCC, US
Flight conditions: IMC
Weather elements / visibility: Thunderstorm; Turbulence
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Weather; Procedure
Primary problem: Weather

Narrative: We had multiple small to medium size thunderstorms in the area departing LAS and encountered frequent light to moderate turbulence during our climb.  We were able to avoid most of the strong radar returns.  As we passed BTY we advised ATC that we needed to deviate West around weather ahead.  ATC advised us that if we could go North then we would avoid weather near OAL as well and would be clear past OAL.  We had just enough time to turn North and still avoid the weather.  I was insuring the Flight Attendants were still seated. I noticed that the First Officer was turning closer to the weather. When I realized that ATC had requested that the flight turn towards the weather I advised that we would be unable to do so. When told by ATC that there was a restricted area ahead; I [used captain's] and told ATC that we would not fly any further west and to contact the airspace authority for said restricted area.




Synopsis: B737 Captain reports being unable to comply with ATC instructions to avoid restricted airspace while deviating around thunderstorms and tells ATC to inform the restricted airspace controlling authority of his presence.
Date: 201411
Local time of day: 1201-1800
Location: TWF.Airport, ID
Light: Dusk
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operating under: Part 91
Flight phase: Landing
ATC / advisory: Tower TWF
Reporter function: Pilot Not Flying; First Officer
Second reporter function: Captain; Pilot Flying
Anomaly: Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport
Primary problem: Airport

Narrative: Immediately after touching down to land; two animals ran perpendicular to the runway in Twins Falls. A fox caught our eye which was then followed by a coyote. We felt a sudden but slight swerve to the right and heard a 'thud.' The Captain was pilot flying and continued the roll out without incident. Thrust reversers were deployed at or shortly after the time of impact with the animal. No damage to the gear was perceptible but we informed tower as soon as possible and a fresh animal carcass was found by airport authority.


Second narrative: [Report narrative contained no additional information]


Synopsis: A small transport jet flight crew reported they ran over a coyote on landing roll in TWF; no apparent damage to the aircraft.
Date: 201711
Location: ZZZ.ARTCC, US
Aircraft: B737-700
Operator: Air Carrier
Mission: Passenger
Flight phase: Climb
Aircraft component: Autopilot
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew FLC Overrode Automation
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: During climbout; approaching the flight levels the autopilot pitched down rather quickly to maintain the climb speed schedule with VNAV engaged. To make the flight more comfortable the Captain elected to use V/S to continue the climb to FL390. Approaching the low FL300s I began looking in my publications and took my eyes off the instruments. Shortly thereafter the Captain gasped and I looked away from the EFB and noticed our airspeed had deteriorated significantly since I last looked moments earlier. The aircraft was at a speed just shy of the amber header. Meanwhile the Captain lowered the nose to gain speed. Altitude loss was minimal and this occurred around FL370. ATC never queried us and we continued our climb to FL390 once the aircraft returned to a normal energy state. The Captain noted the MCP window had a flashing A. No other buffet alerts or stall indications were activated.


Second narrative: [Report narrative contained no additional information.]


Synopsis: B737 flight crew reported that during climb the autopilot pitched over to regain airspeed.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: Caravan Undifferentiated
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Workload; Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Altitude Overshoot; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued New Clearance; Flight Crew Regained Aircraft Control; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Weather; Software and Automation; Human Factors; Airspace Structure
Primary problem: Airspace Structure

Narrative: Aircraft X was level at 10;000 feet westbound to ZZZ. The pilot asked for a block 10;000 to 12;000 feet; which I issued. Lots of aircraft were taking that same block due to weather in the area. Shortly after the minimum safe altitude warning sounded; and when I looked; Aircraft X was at 7;100 feet in a 5;000 feet minimum IFR altitude. Confused; I continued to watch and realized it was sounding because the aircraft was dropping so rapidly. Knowing something was definitely wrong I reached out to the pilot; but no response. After the aircraft went from 7;100 feet to 6;400 feet to 2;400 feet; I reached out two more times with no response.Finally; the pilot responded and requested descent to 1;000 feet and I informed them they were in a 5;000 feet minimum IFR altitude. They then canceled IFR but never descended and actually climbed to 2;800 feet. Eventually they reached 5;900 feet and requested to return to ZZZ1. A clearance was issued direct and assigned 6;000 feet which they had requested but then climbed to 7;000 feet; so I just issued 7;000 feet. The pilot was very shaken up. It sounds like a software issue? I recommend fixing that or grounding the C208's until it is fixed.




Synopsis: A Center Controller reported a C208 rapidly descended below its assigned altitude; was not responding to ATC calls; and flew below the Minimum IFR Altitude; later the pilot established communications; climbed to a safe altitude and returned to its point of departure.
Date: 201702
Local time of day: 0601-1200
Location: VNC.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class G VNC
ATC / advisory: CTAF VNC
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: [I flew] to VNC for lunch. There was a considerable traffic load at VNC and I sequenced behind another aircraft; also via the crosswind entry. I made position calls on each leg of the pattern; and twice on the downwind leg. I turned my base leg after the aircraft in front of me passed my wing. Spacing was perfect and the aircraft in front of me landed without event. While on the base leg (landing aircraft on short final); I saw [another aircraft] taxi up in the #1 position at the hold short line. I had been watching them and they held for less than one minute (a short period; considering all the sequenced landing traffic). After I announced a 'turning base to final' call; the [other aircraft] announced their intentions to lineup and wait. I immediately said; 'Sir I am on final'. This was ignored when I saw the [other aircraft] start to move forward. I immediately queried 'What are you doing?' They did not respond. As the [other aircraft] continued to move toward the runway; I announced; 'I am on short final. Stop!' This announcement was also ignored.  Once the landing traffic cleared the runway; the [other aircraft] announced their intentions to depart (no direction specified). I estimate my altitude was 100 ft AGL at the time and since there was an immediately conflict; I announced and executed a go-around.While on the upwind leg (right side-step); I asked the [other aircraft] what their intentions were so we wouldn't have another conflict with them. This time they finally replied; and stated they were going to fly the coast line. After flying another lap in the pattern; I landed without incident. It's also worth noting that there was no other traffic behind me.This pilot's impatience; disregard for safety; failure to effectively communicate; and inability identify traffic on short final; had nearly resulted in an aviation accident at VNC yesterday.




Synopsis: GA pilot reported executing a last minute go-around from 100 AGL when another aircraft taxied into position on the runway at VNC.
Date: 201709
Local time of day: 0601-1200
Location: ZBW.ARTCC, NH
Aircraft: Small Transport; Low Wing; 2 Recip Eng
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class A ZBW
ATC / advisory: Center ZBW
Second aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Procedure; Human Factors
Primary problem: Ambiguous

Narrative: During the ILS 18 approach at LEB we began our descent when we captured the glideslope. When emerging from the cloud base we saw a small twin flying northeast across the approach course. We verified that the airplane was not climbing or performing any maneuvers other than straight and level flight. The airplane crossed below us approximately 200 feet below our altitude. We notified the tower and they informed us that they were not talking to anyone. The tower checked with Boston Center and found out that the aircraft was no longer under their control and was last under radar contact well east of the field. We continued our approach and landed without further incident.




Synopsis: Air taxi pilot reported a near-mid-air-collision on approach to LEB when another aircraft passed below without communication.
Date: 201310
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
Mission: Passenger
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: DC Ram Air Turbine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were departing mid-morning during VMC conditions. The First Officer was the pilot flying. Everything was normal up to and during the takeoff roll. Shortly after rotation; the ADG deployed. After running the After Takeoff checklist; I ran the QRH; and we planned to return. While the ADG was deployed; we noticed that all electric indications on the electric synoptic page appeared normal; and all buses were powered. The only unusual EICAS message was the amber 'L Windshield Heat' caution message. There were no messages pertaining to the electrical system. We of course had not touched the ADG manual release handle. With all indications appearing normal; it appeared that the ADG should not have deployed. Due to the uncertainty of the ADG; and the noise in the flight deck; we decided to return for a normal landing. We checked the fuel and anticipated landing weight; which was right at the maximum. We notified the Dispatcher via ACARS; and the flight release was amended. We notified the Flight Attendant as well as the passengers that we were returning for a normal landing; and the reason. The flight was concluded without further incident. The ADG deployed when it apparently didn't need to. This resulted in a high workload to run checklists and prepare for an air return; all while the ADG was creating a noisy flight deck.




Synopsis: CRJ200 Captain experiences an ADG deployment shortly after takeoff for no apparent reason. The crew elects to return to the departure airport for an uneventful landing at maximum landing weight.
Date: 202109
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other General Ramp
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Ground Personnel
When detected: Routine Inspection; Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Tires and brake were on DSTG but I did not put them on [aircraft]; did not show at the gate. I did pit [brakes] by mistake; thinking that the tires were going to show up on time; but never did and I forgot to take them off on the scanner before closing the flight; causing a weight discrepancy.




Synopsis: Air Carrier Ground Personnel reported listing tires on DSTG (Departure Staging Guide) which did not arrive prior to aircraft departure.
Date: 202111
Local time of day: 1801-2400
Location: ZID.ARTCC, IN
Flight conditions: VMC
Light: Night
Aircraft: Medium Transport
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZID
ATC / advisory: Center ZID; TRACON CMH
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Distraction; Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: Chart Or Publication; Procedure; Airspace Structure; Human Factors
Primary problem: Chart Or Publication

Narrative: On the initial descent into OSU at 24;000 feet; we were issued a clearance by Indianapolis Center to 'Descend and maintain FL230; then descend via the JAKTZ.1 Arrival landing west.' The Pilot Not flying advised ATC that we could accept the first part of the clearance to descend to 23;000 feet; but requested clarification on what the bottom altitude of the JAKTZ.1 Arrival is landing OSU since the Jeppesen chart dated '6 AUG 21' and 'Eff. 12 AUG 21' depicted no altitude landing East or West instructions at the final fix 'RIBLE' for OSU arrivals. The Controller was off frequency for 30 to 60 seconds and was unable to provide an answer; only that Columbus Approach would be able to answer. At that point the crew confirmed that the only logical altitude clearance limit would be JAKTZ intersection between 16;000/10;000 feet; so they set the altitude pre-select for 10;000 feet and armed the Vertical Navigation. The first Columbus Approach Controller also could not provide an answer; but the second Columbus Approach Controller took us off the arrival and assigned a heading and altitude. This Controller did inform us that there was an error in the new arrivals for the Columbus satellite airports and that the altitude for OSU arrivals was inadvertently omitted on from the current chart. This omission has caused considerable confusion since the new arrivals went into effect in August. A Notice to Airmen should be issued in the short term and the procedure should be revised and published as soon as possible.




Synopsis: Captain reported the JAKTZ.1 STAR to OSU does not have the bottom altitude published on the charts. The TRACON Controller advised the pilot this was an error and a known problem.
Date: 201508
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke; 6
Light: Daylight
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Descent
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Human factors: Situational Awareness; Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Gear Up Landing
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Accompanied by a friend; I was flying short trip (25 minutes) to have air conditioning charged. Had recently installed a new battery and intended to have charging system (alternator; voltage regulator) inspected by mechanic before upcoming trip. Fires in the area made for very hazy conditions. About 15 miles out; while speaking to approach; after establishing communication; I began to experience electrical failure. Radios fluctuated with loud whining noises; electric gauges and lights in plane cycled off and on with increased frequency. I notified approach that I was experiencing an electrical problems and would still like to land. Through the static; they told me to look for a green tower light and to descend to pattern altitude; then ATC cleared me to land. My radios failed completely at that point. At the sign of electrical problems; I lowered the gear handle about 8-10 miles from the field and descended to pattern altitude 1;300 feet; flew a downwind and right base and turned final. Everything seemed normal under the circumstances. I was shocked to land gear up on the runway centerline. We came to a halt and exited the airplane without incident. I realized that I had failed to confirm that the gear was down and locked by looking out the window as the gear down light was inoperative.




Synopsis: C210 pilot experienced electrical failure after having a new battery installed. The landing gear is selected down 8-10 miles from the field but the landing gear indicator lights have failed. A gear up landing ensues.
Date: 201910
Local time of day: 1201-1800
Location: ZOB.ARTCC, OH
Flight conditions: VMC
Light: Daylight
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Corporate
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZOB
ATC / advisory: Center ZOB
Aircraft component: GPS & Other Satellite Navigation
Component problem: Failed
Reporter organization: Contracted Service
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface; Distraction; Confusion; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation - Altitude Undershoot; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Aircraft Equipment Problem Dissipated; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem
Contributing factors: ATC Equipment / Nav Facility / Buildings; Aircraft
Primary problem: Aircraft

Narrative: Routine return flight. Everything was normal up until our climb from 28;500 thru 29;000 feet when suddenly the autopilot annunciation sounded and then followed by a complete GPS failure. We let ATC know the issues we were dealing with and they gave us a heading and an altitude. I was currently the Pilot Flying and given 27;000 feet. On our descent back down to 27;000 feet; we were working hard to get the avionics issue figured out and I believe there was a miscommunication between the Pilot Flying and Pilot Monitoring regarding our selected altitude. Workload was at its peak and we leveled off at 28;000 feet momentarily. While hand flying; we determined flight guidance system 1 and 2 had failed. ATC gave us off route vectors and were very understanding of our situation and very patient with us. It was about 30 seconds between our brief level off at 28;000 feet when ATC politely asked us to descend to 27;000 feet when workload permitted. We made our descent to 27;000 feet and after about a total of 5 minutes; we regained GPS signal and Flight Guidance system began working as normal. Crew coordination and verifying altitudes during an abnormal operations like we experienced should have remained an essential item to cross check and confirm.




Synopsis: A pilot reported they temporarily lost the GPS signal.