elihoole/asrs-aviation-reports huggingface dataset:
Date: 202003
Local time of day: 1801-2400
Location: ZAB.ARTCC, NM
Flight conditions: VMC
Light: Night
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class B ZAB
ATC / advisory: Center ZAB
Aircraft component: Powerplant Lubrication System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; Flight Crew Diverted; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In cruise at FL380. Noticed right engine oil quantity indicated 4 qts. Went to QRH and followed procedure. Oil pressure and temperature indications were normal and pretty much matched the left engine. Continued to monitor as directed. Called dispatch on crew phone ( which worked great BTW) and gave him a heads up. Agreed that we would continue with diverts ahead of ZZZ; ZZZ1 and ZZZ2. Quantity indication continued to decrease slowly over the next hour. Pressure and temperature were normal. Approximately abeam ZZZ1 we asked to descend to FL 300 due to turbulence. At idle power; oil pressure and temperature remained normal and basically matched the left engine. However; at level off when power was increased; we noticed that the right engine oil pressure began to noticeably fluctuate and decrease. We immediately [advised] with ATC and began a diversion to ZZZ2. With right oil pressure at or near the red line limit; we elected to shut down the engine. Complied with QRH procedures and executed an ILS/visual single engine approach to RWY 26. ARRF was standing by. We cleared the runway and stopped on the parallel taxiway. ARRF crew checked out the right engine and advised that there were no issues. They followed us to gate A-9. Maintenance met us at the gate and were debriefed.




Synopsis: B737 Captain reported decreasing oil quantity on right engine at cruise with subsequent fluctuating pressure and quantity resulting in an inflight engine shutdown and diversion to make an priority landing.
Date: 201910
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Mission: Ferry / Re-Positioning
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Fatigue; Communication Breakdown; Situational Awareness; Time Pressure; Workload
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Aircraft; Procedure
Primary problem: Human Factors

Narrative: We were repositioning an aircraft from ZZZ-ZZZ1 and we got a 'RAT FAIL' message on landing. Maintenance was notified and it was written up. We then learned that the circuit breakers were out on the MCDU (Multi-purpose Control Display Unit); meaning we failed to check the status of the circuit breakers on the MCDU during the originating/receiving checklist. While we had thought we checked it when we got on the airplane; it seems we had missed it and didn't get a message alerting us until we landed. Factors that caused this omission included falling into the bad habit of thinking things have been checked even if they haven't; rushing through checklists without making sure the steps have been completed; and tiredness from an early morning show with 2 repositions with maintenance and bad weather. Because we frequently hit the CB button on the MCDU; it's easy to think you've already looked at the page and verified it has been done; because of complacency. The reason there are 2 pilots is to catch each other's mistakes. Today we missed an important part of a checklist that didn't result in any safety concerns for today; but easily could have been a problem if other issues arose. For next time; I will remember to slow down and make sure each checklist item is completed; instead of getting in 'autopilot' mode and thinking things have been done before they have. There are no suggestions for any procedure changes as this was a simple accidental omission of a checklist item that should have caught the problem.




Synopsis: EMB-170 pilot reported failing to check status of circuit breakers before departing.
Date: 202004
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Technician
Human factors: Other / Unknown; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure; Company Policy
Primary problem: Company Policy

Narrative: Myself and partner were assigned to work Aircraft X that arrived with 2 open log pages that concerned me and my partner about our safety and health at risk. My partner was assured that the aircraft was going to be deep cleaned. We were assigned to do a tire change and 1 svc and had to enter the flight deck to do work. As I entered the aircraft I spoke to the lead cleaner and had asked if they were concerned about what happened. To my surprise they were not aware of the COVID-19 contamination and sick pilots in the flight deck and I also asked if there was a special cleaning group to sterilize the flight deck. I think that the cleaners were the only ones that did their regular cleaning job and were not informed of what happened. I was really surprised that there is not an organized process for this type of situation. I thought that entering this type of contaminated aircraft would be really strict.




Synopsis: Technician reported an aircraft was supposed to be deep cleaned after possible COVID-19 contamination; but when cleaners where questioned they had not been advised to deep clean the aircraft.
Date: 201505
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: As [a] Flight Attendant (FA); my assigned jump seat [on this flight] is 2 CTR L. From this jump seat; there is no access to the interphone. Should something happen to the other FAs; such as a rapid decompression; or in the event that they are needed to vacate their jump seat; I have no access to communication with the flight deck or the rest of the crew from this jump seat. I don't feel this is a safe situation. If we had non-working crew seated at the jump seat; they would have access to the interphone; but I would not.There is access from the jump seat at 2 CTR R. I chose to sit at this jump seat for landing; since I didn't feel safe doing so from my assigned jump seat.Not all 767s have this issue. Some have the interphone on the right side of the jump seat at 2L instead of the left side.




Synopsis: Flight Attendant reported he is unable to reach the interphone from his assigned seat in particular B767 aircraft.
Date: 201706
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: UNICOM ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Personal
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Other / Unknown; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: While descending for landing; a cushion which was under the passengers back; came out and hit the left eng prop; which caused a shutdown. An uneventful landing was made on the remaining engine. All repairs will be made by the local Rotax trained mechanic. The aircraft is presently hangared and will remain so till repaired. Being a pusher aircraft [with an open cockpit]; better supervision will be required to make sure everything is strapped down an nothing can exit the aircraft.




Synopsis: Aircam pilot experienced an engine failure during descent when his passenger allowed a cushion to depart the aircraft and pass through the left engine propeller shutting it down.
Date: 202101
Local time of day: 1201-1800
Location: ELM.TRACON, NY
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class E ELM
ATC / advisory: TRACON ELM
Aircraft component: Engine
Component problem: Failed
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Procedure; Manuals; Human Factors; Chart Or Publication; Airport
Primary problem: Procedure

Narrative: I was working Approach Control and received a call over the landline from ZNY Center about an emergency aircraft that was diverting that had an engine failure and was going to be landing. They checked on normally with me and said they were expecting a normal approach and landing at the airport and were getting set up to receive the approach clearance. They were given vectors to help them descend and they advised when they were ready to accept the approach clearance for the ILS approach. They then flew the approach and landed safely. Emergency vehicles were standing by; but not needed. It was brought to my attention that the ILS approach was not authorized in the NOTAMs. I had been briefed that changes were made to the approach plates for the ILS approach and was informed that the changes went into effect four days prior. It was not clear and I was not aware that the ILS approach was not authorized at the time the emergency aircraft used the approach.Clearer guidance is needed from the FAA once changes are made to approach plates.




Synopsis: Approach Controller reported issuing a clearance for the ILS approach; only to discover later that ILS approaches were not authorized per the NOTAMs.
Date: 201710
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: UAV - Unpiloted Aerial Vehicle
Operating under: Other 107
Flight phase: Cruise
Airspace: Class G ZZZ
Reporter organization: Personal
Reporter function: Observer
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Security; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Observer
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I observed an unmanned UAS hovering stationary in the immediate vicinity of the [concert event] stage at approximately 250 AGL in close proximity to a large pyrotechnic display associated with the concert performance. In my opinion; this operation was unsafe and should have been prohibited in light of recent events by the establishment of a TFR for security purposes.




Synopsis: A ground observer reported noticing a UAV was operating near the stage at a concert event.
Date: 201812
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Light: Night
Aircraft: PC-12
Operator: Fractional
Operating under: Part 91
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Chip Detector
Reporter organization: Fractional
Reporter function: Captain
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In cruise climb in an attempt to find smoother air; we were climbing from FL230 to FL270. At approximately FL260; the Crew Alerting System alerted in reference to an 'Engine Chip' condition. We ran the QRH checklist and alerted ATC to the problem and were diverting to ZZZ. After stating that we were not declaring an emergency; but could not accept any delays in our descent; they stated that they were '[advising] on your behalf.' They then cleared us to descend to MVA and began vectoring us on to the RNAV approach for Runway XX at ZZZ. After an uneventful descent and landing; we parked the airplane and shut down.




Synopsis: PC-12 Captain reported a chip detector indication.
Date: 201907
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Situational Awareness; Training / Qualification; Communication Breakdown; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Maintenance; Person Other Person
Contributing factors: Procedure; Human Factors; Company Policy
Primary problem: Company Policy

Narrative: I was brought into an investigation in the Front Office. During the investigation; I was asked about numerous reports that I previously filed including but not limited to [previous] reports and about the numerous investigations I was brought into. I trusted the information that I provided be kept at the highest confidentiality as is stated in the report program. I was never made aware that there is a camera in the room recording audio and video of our meeting; and that other managers are able to watch; listen and review as confirmed by [other] Manager after the camera was discovered. The confidentiality of the program has been continuously breached by Management. It was never disclosed to me or my stewards at any time that we are being recorded by a camera in the room. Since I was in numerous investigation including but not limited to [various dates] but was never told about being recorded.We discovered the camera after the investigation and it was pointing directly at us throughout the numerous investigations. There are also numerous phones and or devices on top [of] the table where the investigations are held. This conference room was used for investigations against me; [Company reporting system]; attendance and ADA. I have reported on numerous occasions to Manager; training courses; broken links; illegible pages; pages moving too quickly; pages moving un-commanded; unrealistic times in course completion that does not reflect or take into consideration the numerous links or material that must be accessed and read for the material which is presented within these courses. [Company] policy forbids retaliation and it states: anyone including managers and supervisors and regardless of position or title will be disciplined up to and including termination. Manager has harassed; threatened and retaliated against me and continues to do that every day and Management is not allowing me to work on planes which I am qualified to do; preventing me from working on any 787s or ETOPS planes. I am continuously singled out by Management; harassed and threatened for reporting concerns; which is a direct violation of but not limited to policy; FAA FAR's; OSHA and [Union] contract.




Synopsis: Maintenance Technician reported confidentiality breaches by Company Management.
Date: 201312
Local time of day: 1201-1800
Location: ZNY.ARTCC, NY
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Flight phase: Climb
ATC / advisory: Center ZNY
Reporter organization: Fractional
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Distraction; Workload; Troubleshooting
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight; Pre-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Chart Or Publication; Airspace Structure; Procedure
Primary problem: Airspace Structure

Narrative: I (First Officer) called Clearance Delivery in HPN and received a clearance to a Caribbean destination. While entering the route in the FMS; a fix called KINNG was not recognized in the FMS database. I contacted Clearance Delivery a second time to verify spelling. I had the correct spelling according to the Clearance Delivery Controller so I then began looking in JeppFD for KINNG. I located KINNG about 120 miles northeast of HPN. I then called Clearance Delivery a third time to question the switchback in the routing. He then called New York Center to confirm routing over KINNG which was confirmed to be correct. He then stated he had given that same routing to several other aircraft earlier in the day and that if we wanted different routing there would be a significant delay. We assumed KINNG was just missing from the database and defined KINNG with coordinates from [my EFB.] After reviewing the routing downstream; we discovered another switchback. I called Clearance Delivery a fourth time and he in turn called New York Center which corrected the issue. After departing HPN; we were given clearance direct to KINNG Intersection. Shortly after; we were asked if we were heading direct to KINNG. I responded yes; he then told us to turn right to a heading of 190. I informed ATC that we were showing KINNG dead ahead. I then asked for the spelling for KINNG and the Controller first spelled it KINNG; but in the background you could hear another Controller saying' no; it's KINGG'. Our Controller then said no; it's KINGG. We then entered KINGG in the FMS and informed ATC we could proceed direct to KINGG without further incident. Two fixes in same area with like spellings...ATC giving us the wrong fix.




Synopsis: A flight crew departed HPN with a clearance northeasterly to KINNG and discovered after a track deviation that ATC confused that fix with KINGG which was located 230 NM southeast.
Date: 202012
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
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: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Result: General Flight Cancelled / Delayed
Contributing factors: Human Factors; Company Policy; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: Flight Attendant was preparing for door closure checking bins and seat belts. Upon reaching Passenger X in XX2 noticed young man mid twenties wearing mask below his nose. She asked him to pull his mask up and got no response. She motioned to him to get his attention and repeated herself; but he just stared straight ahead in defiance. She had to repeat herself and asked if he understood English. He made an eye roll and told her; 'You can leave now;' dismissing her instructions.The Flight Attendant approached the cockpit and told me the situation. We were now past departure time and I stepped back to reiterate the mask policy verbally. When I approached his seat; he was staring straight ahead with the mask just barely over his nose. I explained Airline has a mask policy for everyone on the airplane except when actively eating or drinking; and that he was not being singled out and needed to follow the instructions of the flight attendants. His response in a raised voice was; 'I'm wearing the [expletive] mask!' and 'You're making me angry.'I asked him why he was angry and then what he thought he would do when he got angry. He just tried to stare me down and I decided there was no point in continuing this conversation with him. I made the decision to have Customer Service remove him from the full flight to prevent anymore altercations once airborne.




Synopsis: Air carrier Captain reported having a passenger removed from a flight due to non-compliance with face mask policy and passenger misconduct.