elihoole/asrs-aviation-reports huggingface dataset:
Date: 201807
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Beechcraft Twin Turboprop or Jet Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Photo Shoot / Video
Flight phase: Cruise
Reporter organization: Personal
Reporter function: Captain; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Heading north making two passes at 500 feet AGL altitude to gather photographs; I noticed on the second pass two paddle boards about 2 miles out in the water with only one person standing waving his/her paddle. I made a 270 degree turn and dropped down to see if there really was a problem. After the lower pass heading east; I could see two people now standing; without life preservers; but now paddling towards the shore. During this pass; I pulled up hard while crossing over the end of the point and may have been below 500 feet as I crossed over the houses. Strong winds can and has caused problems with these paddle board people so about 10 minutes later I again flew over the site at about 800 ft AGL to confirm they were making progress toward shore in the strong wind.




Synopsis: King Air pilot reported possibly flying too low over houses.
Date: 201702
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were in a Piper Archer practicing a soft-field takeoff. During the takeoff phase the student pilot did not input enough right rudder correction and we began to swerve to the left. I was the flight instructor and had to immediately take the flight controls before we veered off the runway. I took the controls and immediately brought the takeoff power to idle; stopped the plane and taxied off the runway.




Synopsis: PA-28 instructor pilot reported a rejected soft field takeoff when his student lost control during takeoff roll.
Date: 201410
Local time of day: 1201-1800
Location: ZDV.ARTCC, CO
Aircraft: B737-700
Operator: Air Carrier
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZDV
ATC / advisory: Center ZDV
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Second reporter function: Captain
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: A B737-700 was handed to me from 28 on the wrong arrival; since we had just changed arrivals...again.  When he checked in I gave him the a new clearance like: B737-700 cleared to den via after clapton join the jagger3 arrival; descend via the jagger3 arrival; den altimeter is ....   I believe he read back something like : ok back on the jagger arrival we'll descend via the jagger arrival. Followed by the comment that this was their 4th! arrival change in the last 10 minutes!I noticed a little later that he was to high and to close to the gate and asked if they were descending via and would make the restriction. Their read back was almost of confusion and uncertainty; of which I took as a no/not sure.  I called approach saying he was high and was told that there was nothing that they could do with him; so I descended him to an altitude and gave him a left heading.  After looking/talking to the sector above me; whose airspace he was in; I found a hole to put the aircraft back into.  So after a couple of headings and descents; I had alerted him that I was going to change his arrival again and put him in a different stream; he fit in that hole with no issue and went in without further issue.We were also metering during all of this also.This new RNAV arrival is a mess; as I know there is already paperwork about.  Along with DEN approach changing the configuration every 5 minutes is ridiculous.  I'm sure that there is more of this type of thing happening than I know of.


Second narrative: During the arrival into Denver; we were changed from the JAGGR3 to the PURRL; back to the JAGGR Arrival; as we approached Denver. While we were reprogramming the computer; ATC asked if we had begun our descent on the second JAGGR Arrival. Neither one of us remembered ATC giving us a 'Descend Via' clearance and we notified ATC at that time. ATC vectored us off the arrival for a descent and then put us on the ZPLYN Arrival. Remainder of the flight was normal.


Synopsis: ZDV Controller described a missed crossing restriction by a DEN arrival; the flight crew commenting about a number of STAR changes by ATC.
Date: 202003
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: No Aircraft
Reporter organization: Government
Reporter function: Enroute; Oceanic
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Other / Unknown; Troubleshooting
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Procedure; Staffing
Primary problem: Staffing

Narrative: I reported to work today for the swing shift. Before coming in; the facility had restarted oceanic traffic with the exception of ZZZ airspace. ZZZ airspace was only going to be staffed due to the Coronavirus situation 'As Needed.' This meant that any overflight traffic was restricted to flying around ZZZ radar volume as the airspace is not going to be staffed. As a result; aircraft would be inconvenienced and rerouted around a 360 NM diameter of airspace.We regularly when there are radar outages at ZZZ; put the higher altitudes (Usually FL320 and above) into the ATOP system allowing the ATOP controller to work that airspace volume. This operation allows overflights to fly through ZZZ utilizing NON RADAR rules at the higher altitudes. This operation would allow the airspace to be used without inconveniencing the aircraft operating there. This was suggested but rejected by the union for unknown reasons. Then Sector X could be staffed as needed for the approach into ZZZ purposes only.




Synopsis: Center Controller reported that under-staffing due to COVID-19 has resulted in numerous aircraft reroutes.
Date: 201703
Local time of day: 0601-1200
Location: SNA.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E SCT
ATC / advisory: TRACON SCT
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Human-Machine Interface; Distraction; Workload
Anomaly: ATC Issue All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Pre-flight; In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Chart Or Publication; Procedure
Primary problem: Procedure

Narrative: There is NO pilot deviation or safety issue this flight because we planned ahead and we're ready. This report is for information only and to prevent other possible pilot/ATC deviations. There is a point on the DSNEE1 RNAV that is not possible to achieve. We saw this in advance; we asked for relief; we were given latitude to deviate from SoCal Approach Control; we tried to make the restriction and were unable; we brought this up to ATC controller's attention and he was in agreement. Upon loading the FMC before departure the 'TOO STEEP' message repeatedly appears for the next three hours. The issue is this: on the DSNEE 1 RNAV into SNA the crossing restriction at ROADE between 19000 and 17000 is too high so as to cross the next point PHIYA at or below 13000 within 11.3 NM at 280 kts. This exceeds the capabilities of the B737. SoCal ATC is aware of this; there have been other reports on this specific route structure; this needs to be changed.




Synopsis: B737 Captain reported the SNA DSNEE 1 RNAV Optimized Profile Descent (OPD) altitude constraints between ROADE at 17;000-FL190 and PHIYA at or below 13;000 ft are beyond B737 descent capabilities.
Date: 201707
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb at about 2;000-3;000 AGL we received low oil quantity indication (24 percent) from the right engine which was accompanied by the reverse video box surrounding the engine parameters. This was the second leg flying this aircraft and quantity before takeoff was 75 percent. With the low oil quantity and high EGT on the right engine only; we arrested our climb at approximately 7;000 to see if the oil quantity would rise and the EGT would decrease. The temperature dropped some but not very much; and the oil quantity was slow to rise. When it did; we decided to climb on the SID to 13;000 and requested a vector to investigate. The oil quantity returned to 24 percent and the EGT was close to 900 degrees C. ATC inquired if we had a problem. We requested vectors to discuss working a plan out. Also via ARINC the issue was given to Dispatch. With the pooling of resources; and in the interest of safety; the decision was jointly made to divert to [a nearby airport]. We requested delayed vectors; ran checklists; alerted the Flight Attendants and informed the passengers. Upon landing; the Dispatcher; Chief Pilot on Call; and Maintenance had a phone call debriefing. The Maintenance person; who met us at the gate; informed us there was some pooling of oil around the right engine.


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


Synopsis: B737 flight crew reported diverting to an alternate airport after noticing low oil quantity and high EGT on the Number 2 engine.
Date: 201912
Local time of day: 0601-1200
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Escape Slide
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Communication Breakdown; Time Pressure; Troubleshooting; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: In-flight
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Manuals; Company Policy; Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X parked at [gate]. The flight crew reported in the logbook that L2 door was hard to arm; an ARMS message was generated to T4 maintenance. Supervisor went up to the aircraft and reported to Flight Attendant in aft galley. Supervisor proceeded to arm and disarm the L2 door without having any maintenance personnel alongside to do the actual work. Supervisor did not have any documentation of any type related to this task. Supervisor did not have the Monitor and Challenge Checklist at hand; nor did he have any AMM procedures on how to lock out and render safe the L2 door; there was no puncture tool at hand when the slide deployed. Finally; there was a mechanic directly outside of the L2 door on a lift when the slide deployed possibly causing serious bodily harm and up to even death. The mechanic who was outside was a [long time] employee of the Company.This event occurred because of Supervisor's lack of knowledge; attention; purposely not following Company's policies and procedures; and not caring for the well being of the personnel that he was hired to oversee. Supervisor has been reprimanded time after time to not engage in performing aircraft maintenance and with his over bearing attitude shrugged off the requests. Upper Management has also been notified each and every time and they have done nothing to have him cease and desist nor have they disciplined him for each and every infraction he has committed. I am truly afraid that the next time he is involved in such an event he will maim or kill one of our employees.




Synopsis: Technician reported maintenance supervisor caused an inadvertent slide deployment due to lack of adhering to company policies and procedures.
Date: 201505
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Aircraft component: Navigational Equipment and Processing
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain
Human factors: Human-Machine Interface; Training / Qualification; Confusion; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Procedure
Primary problem: Procedure

Narrative: This new line normal of First Officers copying their flight displays to the captains side is dangerous and needs to stop! This setup is also done nonverbally so the captain may not know that it has been done. The flight displays are setup indivdually as a crosscheck and to the pilots liking. Lets say the First Officer forgot to select terrain on and the Captain had it on. The Captain leaves the flight deck for something and the barometric altimeter changed. The first officer reaches up to the overhead panel and switches the displays to both on 2; thereby resetting the altimeter but now BOTH displays DO NOT HAVE TERRAIN ON and the other settings the Captain had are now gone. THIS PRACTICE OF USING THE OVERHEAD TO SETUP AND MATCH DISPLAYS NEEDS TO STOP IMMENDIATELY!




Synopsis: A B737 Captain is concerned about first officers selecting FLIGHT DISPLAY SOURCE ALL ON 2 without consulting the other pilot because TERRAIN ON or altimeter settings my be changed or deselected without the other pilot's knowledge.
Date: 201706
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 15
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Mission: Personal
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Captain; Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Conflict Airborne Conflict
Detector: Person Other Person
When detected: Other Notified after flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Airspace Structure
Primary problem: Ambiguous

Narrative: Getting set up for normal VFR landing. After entering the pattern area I reported my position downwind; left base; [and] final approach for Runway 23. I landed on 23 with no incident exited the runway and taxied to the ramp.I received a letter wanting to discuss a near miss. I have no knowledge of any near miss.




Synopsis: GA pilot reported being notified of an unknown near miss event.
Date: 202101
Local time of day: 1801-2400
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We experienced a sudden engine failure on engine 2 while cruising at FL330. While in cruise the planes speed slowly crept up towards red line so the Captain pulled back the power to prevent any type of over speed of the aircraft. He had the power at idle for about 1 or 2 seconds then began to smoothly bring the power up. Either as he brought it up or within a few seconds we felt the engine fail and got an engine 2 FAIL EICAS caution. The Captain continued flying and took the radios as well as he told me to run the QRH. We ran the engine fail QRH and the NAP checklists that the QRH led us to. During this time we attempted an APU assisted restart because we the number 2 engine still had oil; hydraulic fluid; was not frozen and to the best of our knowledge had not taken significant damage. On the attempted restart there was no movement on N1 or N2 at all. At that time we deemed an engine restart was not possible. We also decided on diverting to ZZZ2 while doing this; because we were just passing it; it has a nearly 10;000 feet runway; and we had two alternates because of what we assumed was the possibility of fog later in the night so we didn't want to continue north. We finished all QRH; checklists; and talked to the flight attendants and passengers and made an uneventful landing. After stopping on the runway the trucks checked for damage then followed us as we taxied to the gate under our own power.


Second narrative: Loss of number 2 engine during cruise.Followed QRH; advised ATC; diverted.


Synopsis: EMB-145 flight crew reported an engine failure during cruise that resulted in a diversion.
Date: 201412
Location: SJC.Airport, CA
Flight conditions: IMC
Weather elements / visibility: 2
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Initial Approach
Airspace: Class C SJC
ATC / advisory: Tower SJC
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Anomaly: Inflight Event / Encounter Other / Unknown
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: I want to bring a potential hazard to your attention. During recent storms in the Bay Area; we have utilized Runway 12R ILS at SJC on numerous occasions. The recently completed stadium has a sign on top of the stadium; which when lit at night in poor visibility conditions; appears exactly like a PAPI; being a horizontal bar which is red on the left and white on the right. It appears as if you are on the Vertical Path but off course to the right of the runway. While my Crew; per Company procedure; remained on the ILS guidance had no issue; both of us had to do a double check to be sure as it appears that real. It doesn't become apparent that this is a sign until you actually pass the stadium. While following procedure kept us on course; the visual trickery of this sign could be very easily mistaken for the PAPI for Runway 12R under poor visibility conditions leading an unsuspecting crew to mistakenly correct to the left while descending and subsequently put them on a collision course with the stadium itself. It would be worthy of consideration to issue an alert regarding this issue.




Synopsis: Pilot reported a local stadium's lights could be mistaken for VASI when SJC Runway 12R is in use; especially at night in poor visibility.
Date: 201508
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fire/Overheat Warning
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Distraction; Time Pressure; Workload; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Aircraft Equipment Problem Dissipated; Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: My First Officer and I were climbing through approximately 22;000 feet when the right engine fire light illuminated. Per the emergency memory items I reduced the throttle to idle and a few seconds later the light extinguished. We ran the appropriate checklists for an engine fire and decided quickly that we would divert to a nearby airport. The First Officer informed ATC that we had a possible engine fire and that we wanted to divert. We were immediately given clearance and made an uneventful landing from a visual approach. After shutdown there was no visible evidence of an engine fire on the right engine.




Synopsis: A CE-560XL fire warning alerted during climb so emergency procedures and checklist were completed with the warning extinguished at idle thrust. The flight diverted to a nearby airport where no fire damage was seen.