elihoole/asrs-aviation-reports huggingface dataset:
Date: 202110
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Elevator
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing through 13;000 ft. we got an 'Elevator Split' caution message. I continued to fly the airplane and took the radios while the Captain ran the QRH. The QRH directed us to land at the nearest suitable airport. We decide to return to ZZZ and [requested priority handling] since we had a flight control issue. After completing the QRH the Captain notified the cabin crew and passengers. We also notified ZZZ Operations of our return. Once we were ready to land the Captain took control of the aircraft. Our approach; landing; and taxi to the gate was uneventful.




Synopsis: Air Carrier First Officer reported an 'Elevator Split' caution message during initial climb. The flight crew returned to the departure airport and executed a safe landing.
Date: 201911
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: SA-227 AC Metro III
Flight plan: IFR
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Oil Temperature Indication
Component problem: Failed
Reporter function: Captain; Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon climb out I noticed the Right Hand engines oil temperature start to rise; approximately 2 minutes of monitoring the oil temperature I watched a rise from 100 degrees to past red line just shy of 150. During the rise of oil temperature I consulted the QRH and had it ready to perform the necessary steps to deal with high oil temperature. Passing high red line I started to reduce power to avoid high oil temperature to no avail. I then proceeded with the recommended precautionary engine shutdown and told regional control I would like to return to the airport and will be shutting down an engine while continuing with all required precautionary shutdown and operating engine and single engine checklists from the QRH. Approach control vectored me to [Runway] XXR with no incident getting off at the taxiway where I stopped; shut down and called Dispatch to come tow the airplane back to the hangar. It was a faulty gauge as no oil loss and good pressure prevailed after post flight inspection. No possible way to keep [it] from occurring. Isolated event by equipment malfunction.




Synopsis: SA 227 pilot reported returning to the departure airport after observing a high engine oil temperature; that ultimately was caused by a faulty gauge.
Date: 201409
Local time of day: 1201-1800
Location: JAX.Airport, FL
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Ambulance
Flight phase: Final Approach
Airspace: Class E JAX
ATC / advisory: TRACON JAX
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X checked in about 45 northwest of GNV; I gave the pilot arrival information to expect the RNAV to runway 11.  I sent him to the 10 mile fix for the straight-in; the pilot requested direct to the northern T-fix so I approved it and descended the aircraft to 3000 feet.  I told him to track the approach inbound; I didn't want to clear him at that angle because it would of been illegal.  I was gonna clear him once I saw him established on the approach; but instead I cleared him a mile west of the fix.  The pilot accepted the clearance; but later I got a low altitude alert on the aircraft; so I told the pilot the MVA and he climbed to 2000 feet.  Soon after that I got another alert and the pilot did not appear to be established; so I gave him another low altitude alert.  I also asked if he was established and he said no; so I vectored him around again for the approach; only this time he got vectors to final.I would either unable direct to the T-fix at that altitude; or vector the aircraft to final from the beginning.




Synopsis: JAX Controller approved a short turn on to final for an aircraft; received numerous low altitude alerts and then had to resequence the aircraft for another approach.
Date: 201909
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
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: Galley Furnishing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
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 Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The Flight Attendant called and reported smoke coming from the oven in forward galley. IRO (International Relief Officer) was back on break and described to us over handset the smoke was white and billowing from the oven along with extreme burnt smell. We ran the QRH and advised the Flight Attendant to turn off oven and pull circuit breakers. She stated there was burnt food in the oven; which she thought was the cause but said the oven was unusually hot. After a short time; the smoke dissipated but smell lingered. Discussing with crew; we decided the safest course of action was to divert into ZZZ; with an uneventful over weight landing.




Synopsis: Flight Crew flying 757 reported smoke from galley oven inflight.
Date: 201906
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp ZZZ
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: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Ground Personnel
When detected: Taxi
Result: Flight Crew Regained Aircraft Control
Contributing factors: Equipment / Tooling; Procedure; Human Factors
Primary problem: Human Factors

Narrative: At [time] received 'ramp ready' and completed before push checklist. Received push clearance and communicated with ramp that 'brakes released; cleared to push'. Normal push forces were felt for several seconds followed by a slightly unusual jolt. The tug brought the aircraft to a relatively quick stop. I queried 'did something break'? The tug driver responded; 'I think maybe the shear pin broke'. The aircraft was stationary and I asked the First Officer to cancel our push clearance with ZZZ ramp control. I told the ramp 'pushback canceled'. I don't recall receiving a response from ramp. After approximately 15 seconds; the aircraft began moving aft and I restated 'Stop. Pushback canceled. Cancel Push.' The tug driver stated 'Set brakes. Set Brakes!' The aircraft had moved 3-6 feet in this time. Normal pedal braking was applied to smoothly stop the aircraft and the parking brake was set. Ramp then stated; 'I thought you had set your brakes'. I replied 'I wasn't told to set brakes'. A new tow bar was located; maintenance arrived and provided an inspection; and pushback continued within 3-5 mins. No further issues.




Synopsis: B737 Captain reported on pushback a miscommunication from the ground crew resulting in an uncontrolled movement of aircraft.
Date: 201603
Local time of day: 0601-1200
Location: CRQ.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Helicopter
Operator: Air Taxi
Operating under: Part 135
Flight phase: Climb
Airspace: Class D CRQ
ATC / advisory: Tower CRQ
Reporter organization: Air Taxi
Reporter function: Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Rotorcraft
Anomaly: Aircraft Equipment Problem Less Severe
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: Loss of GPS reception on both the Garmin 530 and 430 units when departing. This happened a few days earlier in almost the same spot. Units both lost reception and regained reception in 3-4 minutes.

Callback: Reporter stated other pilots in his company have not experienced the signal loss.



Synopsis: Helicopter pilot reported loss of GPS signal near CRQ.
Date: 201901
Local time of day: 0001-0600
Location: ZMP.ARTCC, MN
Aircraft: Small Transport
Flight plan: IFR
Flight phase: Descent
ATC / advisory: Center ZMP
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Human Factors
Primary problem: Human Factors

Narrative: As Aircraft X was descending for the approach at CYAG (a Canadian airport controlled by the US) I was quickly reviewing the approach plate for the RNAV 12 and noticed it expired the end of Nov 2018. It has not been updated because those people are on furlough. This caused me to tell the Supervisor and he began trying to get a current copy from Canada and told me to use what I had at the moment. I felt uncomfortable with this so I verified the approach altitudes during each phase with the pilot so I knew what he would be flying and would not be surprised; even if he went missed. This took frequency time and time to check the chart I had; which was time not spent watching the scope. I didn't have much traffic but I was steadily busy completing tasks so no-one would get delayed. I nearly missed a release for Aircraft Y because of the distraction.What if I had missed the date was expired?  What if there had been a change due to a tower or something? I could have caused an accident through no fault of my own. All because Support Staff are furloughed and I don't have the tools I need to do my job safely.Put the Support Staff back to work. They are an integral part of the safety management system. There are only so many layers of safety; and we are eroding them away quickly.




Synopsis: ZMP Controller reported not having current approach plates due to the government shutdown and improvising using an expired plate.
Date: 201710
Local time of day: 0601-1200
Location: SDL.Airport, AZ
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Flight phase: Descent
Airspace: Class B PHX
ATC / advisory: TRACON P50
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Confusion; Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Airspace Structure; Procedure; Human Factors
Primary problem: Human Factors

Narrative: Approximately 20-25 miles east of SDL; we advised Albuquerque we would like to begin our descent to SDL. Albuquerque acknowledged then instructed us to proceed while staying 'north of the 101 Loop'. Concerned about the airspace and unfamiliar with the area; we then asked if a direct heading to Deer Valley would ensure our compliance. Albuquerque confirmed and moments later handed us off to Phoenix. Phoenix then said you have no Bravo clearance and please turn to a heading of 360. We immediately made the turn to the north and quickly accelerated our descent knowing the floor of the Bravo was at 7;000 feet ahead and slightly to the east of our location. Phoenix then said say intentions; we said we are 'heading 360 as instructed and trying to descend below the Bravo. Phoenix then replied that they had already cleared us through the Bravo and to maintain a heading of 360 until further advised. Flustered by the responses; we awaited further direction. Moments later we were given 'own navigation to SDL; stay clear of the Deer Valley Delta; keep the code and contact SDL Tower.'This event was entirely my fault. I should confirmed with Albuquerque that we in fact had clearance when I had asked permission to start our descent. The aircraft is new to me; the area was unfamiliar and I simply made a mistake.




Synopsis: Small aircraft pilot reported poor communication with ATC and unfamiliarity with the area led to an airspace violation.
Date: 202106
Local time of day: 1201-1800
Location: C81.Airport, IL
Weather elements / visibility: Turbulence; 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Corporate
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class B ORD
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Distraction; Situational Awareness; Training / Qualification
Second reporter function: Instructor; Pilot Not Flying
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While flying out to the practice area outside of the Bravo; I was attempting to maintain an altitude 100 feet below the shelf of the ORD Bravo airspace.  There were some up and downdrafts during the first portion of our flight. Based on the altimeter reading in the aircraft I had thought I had caught it in time; but while reviewing radar/ADS-B data on an aviation website; I concluded I did enter the airspace. It was only for a few seconds; but I do take this quite seriously. I believe an additional factor is a lack of flying currency related to the pandemic. In the future; when I feel unstable air; I will select an altitude even lower to provide more of a buffer.


Second narrative: Flying with a private pilot to help him get recurrent. Departed ZZZ and climbed to intermediate altitudes to avoid the Bravo airspace. Pilot selected 3;500 [feet] and acknowledged he would stay clear of the Bravo. He leveled at 3;500 [feet] but then caught an updraft and allowed his altitude to surpass the 3;600 foot floor of the ORD Class B momentarily. He called out that he had allowed the aircraft to climb 100 feet high and I immediately commanded a descent back to the selected altitude. No other aircraft were in the vicinity. Lack of currency; having been out of the cockpit for months; turbulent conditions; and the distraction of instruction as we were reviewing G1000 operation led to the momentary altitude excursion.


Synopsis: Small aircraft instructor and student reported momentary incursion of ORD Class B airspace; citing lack of recent flying experience as contributing factor.
Date: 202001
Local time of day: 1201-1800
Flight conditions: VMC
Light: Daylight
Aircraft: EMB-505 / Phenom 300
Operator: Fractional
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Pressurization System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In cruise at FL410 dual duct overtemp CAS messages displayed. Ran QRC; donned Oxygen; and began descent to 10;000 ft. Passenger masks deployed at around 25;000 ft. airplane altitude and 15;000 ft. cabin. [Requested priority handling] for immediate descent and diversion. Divert to ZZZ; uneventful landing.


Second narrative: Climbing between FL400 & FL410; we experienced a Duct 1 Over TEMP CAS MSG. Within about a minute we received a Duct 2 Over TEMP CAS MSG. We ran the QRH for a DUAL Duct Over Temp procedure and complied with it. We requested and began a descent to FL370 while running the procedure (which included a 1 minute timing after turning off to see if CAS MSGs cleared). Unable to clear; we needed to turn off bleeds and requested lower altitude as we were now slowly depressurizing the cabin. We [requested priority handling] to get lower. Descended to 10;000 ft.; dumped the cabin and removed our Oxygen masks. We landed uneventfully in VMC weather at ZZZ.


Synopsis: EMB-505 flight crew reported a pressurization problem that resulted in a diversion.
Date: 202106
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke; 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Other VFR Pattern
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Bonanza 33
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine; Other tail wheel
Human factors: Distraction; Confusion; Communication Breakdown; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was on a longish downwind to Runway XX at ZZZ. A local flight school was doing pattern work in a C172 using Runway XX.  AWOS 070v080 degrees at 7 to 9 knots. Then another aircraft called on CTAF to announce they were going to land Runway XY. I believe the flight school C172 pilot or instructor advised Runway XX was in use at ZZZ.  C33 pilot grumbled winds were calm and we should use Runway XY; acknowledging not knowing the local weather as had just departed a different airport a few miles southeast.Then C33 pilot; who at times identified a Debonair and other calls as a Bonanza; called for entering a downwind for Runway XX and I had expected them to follow me as I was established and had made calls for being in downwind for [Runway] XX. However; they turned in front of me; perhaps they had a good visual; but never called out having traffic in sight; until I identify them in my 2 o'clock. Perhaps were not as close as it seemed. I turn a little west and decide after turning base to do a go around as the C33 landed long and was still on the runway. I then executed a standard pattern and uneventful landing. Again the C172 was not a factor.




Synopsis: Pilot in the VFR Pattern at a non-towered airport reported an aircraft on downwind behind them turned in front of them resulting in a NMAC.
Date: 202003
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Procedure
Primary problem: Company Policy

Narrative: I recently worked a flight from ZZZZ to ZZZ. There were no masks on the plane just gloves and alcohol free hand sanitizer which doesn't protect against the virus. When we landed in ZZZ we were instructed to get off the plane; so the cleaners could come on. The cleaners only took garbage off the plane; but they were in full hazmat suits. It is highly concerning that it is necessary for them to be in full protective equipment for a 20 minute trash removal when we work a 10 hour flight unprotected. If we're gonna continue to be out working I would really like to see some improvements for the safety of our flight attendants.




Synopsis: Flight Attendant reported there were no masks on the plane for flight attendant use and was concerned that the gloves and alcohol-free hand sanitizer were not adequate as personal protective equipment.