elihoole/asrs-aviation-reports huggingface dataset:
Date: 201807
Local time of day: 1801-2400
Location: DEN.Airport, CO
Flight conditions: Mixed
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B DEN
ATC / advisory: TRACON D01
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Time Pressure; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: On initial contact with Denver Approach we were told to expect Runway 16L. Within approximately 20 miles of the field we were told to expect the RNP Z approach to 17R. After quickly briefing the approach and programming the FMS; we were then concerned with and discussed a thunderstorm just north of the field and windshear alerts from Approach to other aircraft. While on the downwind I happened to look down at the FMS and realized we just passed the last point on the STAR and there was a discontinuity. About the same time we tried to salvage the approach; ATC told us we weren't on the approach and gave us a vector to fly for the visual. Don't let distractions break habit patterns (close up discontinuity when cleared for RNP approach) and have better monitoring skills.




Synopsis: B737-700 Captain reported a track deviation occurred on arrival into DEN following a late ATC change to the clearance.
Date: 201702
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Vans Aircraft Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Exhaust Pipe
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Workload; Time Pressure; Troubleshooting; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Exited Penetrated Airspace; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cruising at 6;500 feet experienced a sudden onset of engine roughness and corresponding reduction of power. EGT of Number 4 cylinder was negligible. Not knowing the seriousness of the problem; I began evaluating off field landing sights as I trimmed for best glide speed in anticipation of a full engine out situation. I had the sectional in my lap and saw a paved airport nearby; did some mental estimates on speed; rate of descent and concluded it was makeable. I turned towards the airport; selected the CTAF and requested and received active runway so I could plan the direct approach.Next I tried combinations of throttle; RPM and mixture with no success in smoothing out the vibrations. Still able to maintain some power; my attention turned to informing the traffic on CTAF (there's an active flight school there and the pattern was quite busy) that I was inbound with one cylinder out and would be making an expedited landing.Through all this; aviate/navigate/communicate; I did not feel; since the engine had been producing some power; that this constituted an emergency; but I was very anxious that one could develop rapidly depending on whatever was wrong. I elected not to squawk 7700; nor did I feel I wanted to divert attention to changing frequency to Approach and go through the story. I was focused on getting on the ground ASAP.With the runway aligned perpendicular to my flight path and blocked by trees; I spend a lot of time trying to find it. During one glance at the GPS (Garmin 430) I noticed I was probably right on the boundary of the Delta airspace and had descended to 2;000 feet; but moving away from it. I had observed no other aircraft in my vicinity.The landing was uneventful; and subsequent inspection discovered a completely severed exhaust pipe on Number 4.The workload and the anxiety of losing complete power contributed to a possible brief violation of Delta Airspace without contacting ATC.




Synopsis: A VANS RV pilot reported that he detected what he thought was a failed engine cylinder and diverted to a nearby airport. On the ground; he determined the Number 4 cylinder exhaust pipe had severed completely.
Date: 201901
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Bonanza 36
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Diverted
Contributing factors: Aircraft; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: I arrived at ZZZ to take on fuel. After fueling; I taxied to the far end of runway XX. After an initial ground roll for takeoff; I rejected the takeoff because I was not building sufficient airspeed in order to safely depart. I taxied back to the very edge of runway XX; including all of the displaced threshold area; and made a second takeoff roll. Short/soft field technique was used throughout for this soft field with fairly long grass. After becoming airborne; the aircraft struck a tree(s) just past the departure end of XX. I was unsure of what damage the aircraft had suffered; but the propeller/engine was not affected. I called up Approach; [coordinated with them;] and was vectored to ZZZ1 where I made an uneventful landing and taxi.I have 500 hours of flight experience in this airplane. I have used it previously at other; shorter turf airstrips. I did not believe it would be an issue to get in and out of the airpark for fuel. I may have been overconfident given my experience with the aircraft.

Callback: Reporter indicated there was also minor damage to the right wing leading edge; but was not considered to be substantial.



Synopsis: BE-36 pilot reported contacting a tree during departure from a turf airstrip.
Date: 201303
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Light: Dawn
Aircraft: Q400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Initial Climb; Takeoff / Launch
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Cargo Door
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Maintenance; Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Chart Or Publication; Weather; Procedure
Primary problem: Ambiguous

Narrative: Aircraft cabin failed to pressurize immediately after takeoff. Performed the Pressurization Fail Checklist and the aircraft would not pressurize. Held close to the departure airport while discussing possible return to the field (RTF) with Dispatch. Decided to RTF. While preparing for the RTF; Dispatch called us and suggested divert to an enroute airport. We referenced the enroute charts for adequate MEA for us being at 10;000 FT and we were comfortable with proceeding to the divert airport. As we were diverting the cabin rate indicated a 3;000 FPM descent and pressurization returned to normal operation. Maintenance Control seemed to believe it was a frozen aft cargo door seal. 40 miles from the divert airport; Dispatch called again and ran numbers for continuing to the filed airport. My crew and I were comfortable with this so we continued to our original destination. With all our low altitude maneuvering; we were showing arrival tight on fuel so I declared Minimum Fuel about 90 miles from my filed destination. About 15 minutes into our divert; I re-ran the Pressurization Fail Checklist to make sure I didn't miss anything and I discovered that I had completed the checklist at the Flight Attendant notify point. Had I continued the checklist it would have led into the Manual Press Checklist; then Unpressurized Flight Checklist. If it were indeed a frozen door seal; the manual pressurization wouldn't have worked anyway. After discovering this error; the aircraft was pressurizing normally so I felt it was better to not continue the checklist because that would have led us to de-pressurize an airplane which was pressurizing normally.




Synopsis: A Q400 failed to pressurize after takeoff and while the crew considered either returning to land or diverting the pressurization began operating normally so they continued to the filed destination. A frozen aft cargo door seal was the suspected cause.
Date: 201908
Local time of day: 1201-1800
Location: DBQ.Airport, IA
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class D DBQ
ATC / advisory: Tower DBQ
Reporter organization: FBO
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Training / Qualification; Situational Awareness; Confusion
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other Landing
Result: Flight Crew Regained Aircraft Control
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: The winds were calm and skies were clear. I was instructing a student in an Cessna 172; and coming in for landing. It was a normal landing and I was on the centerline and the airspeed was around 65 knots. I felt the main gear of my aircraft touch and then the airplane started to lift on the left side. I tried correcting the aircraft with aileron and rudder which seemed to only agitate it more. The aircraft swung even harder to the right. I decided to go the direction in which the aircraft  was veering as I was concerned with the aircraft flipping. So I went off the runway into the grass and didn't hit any sign on the airport or damage the aircraft. The aircraft was then towed back to the hangar.




Synopsis: A pilot conducting instruction reported losing control of the aircraft while landing and a runway excursion with no damage to the aircraft.
Date: 201911
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight phase: Cruise
Aircraft component: Tablet
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Equipment / Tooling; Manuals
Primary problem: Ambiguous

Narrative: Loss of flight manuals (all 737 manuals) in content locker. I lost all 737 manuals in flight ZZZ to ZZZ1. I needed to check an FRM (Fault Reporting Manual) code and found all manuals were gone (no content) in flight manuals-737. The FOM (Flight Operations Manual) and FRMs were still there. I had used these manuals (737-FRM and 737-FM) on an earlier flight; and many times on recent flights with no problems. I called iPad support when in ZZZ1 and they had me remove content locker from the iPad and reinstall it. This restored content to normal operation. They indicated that they were seeing a high level of failures associated with the new content locker. It's disheartening to see this level of iPad failure in flight when these manuals are needed.




Synopsis: Captain reported all 737 flight manuals were lost from iPad while inflight.
Date: 202107
Location: TVL.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Operating under: Part 91
Flight phase: Taxi
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: IFR flight plan filed TVL - ZZZ. 2 pilots. I was the designated SIC and the Pilot Flying for this flight. We elected to depart VFR and obtain our IFR clearance once airborne. We announced our taxi intentions for Runway 36. We noted a few aircraft in the area either landing or flying by the airport. As we held short of Runway 36 at intersection Bravo; we saw an aircraft on our TCAS at 1;700 feet AGL about 4 miles south of the airport heading toward the airport. I visually acquired the aircraft soon thereafter. After hearing no further traffic advisories from other aircraft; the PIC and I agreed to depart Runway 36. The PIC announced our intentions to depart Runway 36 and no further calls (from other aircraft) were initially heard. As we crossed the hold short line; the aircraft that we visually acquired earlier stated their intention to land Runway 36 and began descending. We immediately stopped the aircraft and told the other aircraft we were past the hold short line; but not on the runway surface. The other pilot acknowledged our location and continued their approach to landing. The PIC reiterated that we were already past the hold short line and the other pilot just acknowledged our location. No attempt to increase spacing through S-turns; a 360 or go around was made by the other pilot as we were stopped between the hold short line and the left edge of the runway surface (displaced threshold). Not knowing how fast the aircraft was going to approach the runway; we elected to stay put and maintain visual contact with the landing aircraft. As that aircraft landed; another aircraft (PC-12) announced their intentions to land while on a left base to final. Again; we announced we were past the hold short line but not on the runway surface. They acknowledged our location and continued to land while showing no attempts to increase spacing for us to move our aircraft. After the second aircraft landed; we departed Runway 36 without further incident.




Synopsis: Flight crew reported runway incursion and ground conflict with landing aircraft at TVL non-towered airport.
Date: 201909
Local time of day: 1201-1800
Location: ZZZZ.Airport, US
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Arrival Unloading
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Other Arrival Cargo Unloading
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Incorrect Labeling/build of Dangerous Goods. Cargo was not labeled with dangerous goods label. Dangerous goods box not properly secured to the cargo pallet.




Synopsis: Airline Ground Personnel reported arrival Dangerous Goods box not properly secured to cargo pallet as well as incorrect Dangerous Goods labeling.
Date: 201603
Local time of day: 1801-2400
Location: FLL.Airport, FL
Light: Dusk
Aircraft: A321
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
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Crew member showed up late for van and not in uniform and obviously ill. She said something about a migraine and rode to the airport with her eyes closed. The ride was very long due to rush hour traffic. During the van ride; the other F/A and I were talking and both thought there was no way she could work. When we got to the airport the van driver pulled me aside and told me I needed to do something about her (both that she seemed sick and she smelled sick) the other F/A and I were able to pull the captain aside and share our concerns and the van drivers comments; even telling him that she was not fit to fly. We shared the same concerns with the lead F/A when we got to the airplane. To my knowledge; neither of them spoke to her; and we began to board. We were rushed during the boarding process; even closing the door with bags in the cabin that needed to be checked. After takeoff when the sick F/A came to the back; she went in the lavatory and proceeded to get loudly and violently ill. Myself and the other flight attendant were left to serve and clean up a full 321 by ourselves.I have had some time to think about this; and am extremely disappointed that I feel our concerns about the ability of a crew member to do their duties was virtually ignored. I know we were in an out station; and removing her from the trip would have caused great delays and customer inconvenience; however; that is exactly what should have happened. An ill crew member is often not a very good judge of their own ability and we have an obligation to look out for each other and act in the best interest of our coworkers and passengers. I do not feel I had the tools to do so. We go to great lengths to outline procedures for ill pax; etc. but those were not applied here. We must not fail at our primary duties in order to protect the operation. Without us doing our duties; there is no operation. We need to feel to feel more empowered to do what we know is right.




Synopsis: A321 Flight Attendant reported another Flight Attendant was obviously ill; but worked the flight anyway. This put additional workload on the remaining flight attendants.
Date: 201506
Local time of day: 1201-1800
Location: DVT.Tower, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Mission: Training
Flight phase: Descent
Airspace: Class D DVT
ATC / advisory: Tower DVT
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction; Confusion
Second reporter function: Local
Anomaly: Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Procedure

Narrative: While working the Local Control (LC) North position I had a student pilot call inbound 8 [miles] west at 4500 MSL. I observed two aircraft in close proximity 8 [miles] west of DVT at the same altitude; I asked the one talking to ident. I observed the ident and informed the pilot of the other aircraft doing 360s on an 8 mile final not talking to anyone. The problem is we have a lot of aircraft in that area and the pilot will just go out to the west and do 360s without telling anyone. We have all seen many close calls and we have informed management of this numerous times. It is getting to be a huge safety problem. We need a class delta extension to make sure pilot call us when they are on final more than just 4.5 miles. We are here for the safety of the flying public; let's make sure that we do all we can to make this a safe place.


Second narrative: While working many aircraft; Aircraft X called inbound was initially told to hold outside the airspace. After a few minutes was given straight in runway 7R and report a 4 mile final. There was also another on a final behind him. I then observed someone doing a 360 on a 4 mile final I asked Aircraft X if that was him he replied yes. I immediately turned him south bound and turned the other aircraft north to avoid a collision. This is a huge problem in DVT pilots are doing 360's without asking or even telling the tower. I had been telling the (FLM) Front Line Manager for at least 20 minutes of all the pilot problems I was having; he was listening to me. Then as it got busier he went on break rather than opening up a Cab Coordinator position to help with the flow of traffic.We need the FLMs to help us with pilot education so the frustration doesn't get this high. We also need an airspace extension out to the west so we can have these guys under control.


Synopsis: DVT Tower Controller report of aircraft doing 360 degree turns outside of the Class D airspace. Controllers request an extension to the Class D in this area due to close calls with other traffic inbound to DVT.