elihoole/asrs-aviation-reports huggingface dataset:
Date: 202008
Local time of day: 1201-1800
Location: HNL.Airport, HI
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground HNL
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Confusion
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: On taxi to an intersection L departure for Runway 8L; an intersection I've never used; I became confused of the appropriate place to turn due to confusing airport signage. We were given taxi to 8L at Lima via Taxiway Zulu Alpha Lima. The signage at intersection N makes it appear that this is the correct turn to join Taxiway A. After we made the turn we stopped almost immediately because we realized our error and then allowed a small Cessna to taxi in front of us before Air Traffic Control gave us clearance to continue. Maybe a hot spot marking on the chart; or better signage on the airport grounds would help avoid this in the future.




Synopsis: Air carrier Captain reported he was confused by the signage on taxi out to Runway 8L at HNL airport.
Date: 201507
Local time of day: 0601-1200
Location: NZY.Airport, CA
Flight conditions: Mixed
Weather elements / visibility: Haze / Smoke; 6
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class B SAN
ATC / advisory: Tower NZY
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation 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
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: While flying the 'Channel transition' in the San Diego bay; I was unable to continue around Point Loma and fly north along the coast due to low lying clouds. After returning northbound; I requested the 'Delta transition' to over fly SAN northbound and continue into northern San Diego County. I heard 'Cleared into Class Bravo eastbound' from the North Island Tower and I flew north.When I was abeam SAN; I requested the Delta transition again and North Island tower told me 'Frequency change approved.' Seeing how I had been 'cleared in to Class Bravo' and North Island tower told me to change to SAN; I turned north and proceeded to 1500 and called San Diego tower. San Diego tower gave me a squawk code and I continued northbound. As I passed over the airfield at 1500; tower asked me if I was the aircraft transitioning over the field. I replied yes and the controller informed that she had not cleared me into Class Bravo. I responded saying that North Island had told me that I was cleared into the Class Bravo. She then informed me that North Island cannot clear aircraft for the Delta Transition and let me continue north to Mission Bay. The controller did not give me a number to call; however; I believe this is a point of confusion that should be clarified between the transition from North Island Tower and San Diego Tower. I have flown this transition before (although always North to South) but I believe that North Island Tower should not say anything about clearance into Class Bravo airspace to make certain there is no confusion. All pilots know that 'Cleared in to Class Bravo' are the magic words. So; if they can only get this phrase from one tower; it will help make sure you're getting clearance from the proper entity.




Synopsis: Pilot reports of being cleared through Class Bravo by one Controller; then is shipped to another Tower and checks in. The new Tower Controller questions the pilot and the pilot states the last Controller gave him clearance through the Class Bravo. The new Controller told the pilot that the other Tower cannot issue Class Bravo clearances. The pilot is confused as to why he received the first clearance if that Tower Controller cannot issue it.
Date: 201211
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At cruise ECAM alert of HYD SYS LO PRESS. The BLUE HYD SYS QTY was lost. Communicated with [Operations] via ACARS the malfunction and that an emergency would be declared for precautionary measures. We requested [Operations] to inform ATC in order to coordinate the arrival ahead of time which they did indeed do. The approach and landing were uneventful and we taxied to the gate.




Synopsis: A300-600 Captain reported loss of Blue hydraulic system at cruise. Flight declared an emergency and continued to destination for a normal landing.
Date: 201508
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Daylight
Aircraft: MD-80 Series (DC-9-80) Undifferentiated or Other Model
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: AHRS/ND
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Confusion; Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was the pilot flying; climbing on the SID. Passing approximately 3;000 feet MSL; both navigation displays showed a 'map fail'. I advised the Captain and we asked ATC for vectors and told them that our navigation system had failed. We were given vectors for the remainder of the climb through FL190. Both Directional Gyros (DG) were off of the standby compass in different directions. ATC gave us updated vectors as needed until the system corrected itself. After consulting with maintenance operations; we returned to the departure uneventfully.We checked both headings prior to takeoff and they were correct. The problem arose after takeoff and was a system failure. A timely coordination with ATC for vectors and to relay our needs was critical in complying with ATC's needs as well as our navigation.




Synopsis: MD-80 First Officer reported after takeoff both navigation displays displayed a 'MAP FAIL' alert along with compass errors so the flight returned to the departure airport.
Date: 202101
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cardinal 177/177RG
Operating under: Part 91
Flight phase: Parked
Aircraft component: Propeller Blade
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Situational Awareness; Distraction
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I had parked the plane and positioned my PowerTow to place the plane in the hangar. I noticed that my flaps were down and returned to the cockpit to raise the flaps. Forgetting that the PowerTow was in front of my plane; and not seeing it; I started the engine. The propeller tore into the PowerTow; damaging the propeller. I immediately shut the engine down.




Synopsis: C177 pilot reported damaging the propeller while attempting to start the engine with the tow bar connected.
Date: 202010
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: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate; Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: Numerous passengers wore the mask incorrectly. Both flight attendants and Captain made multiple PAs detailing the importance of proper mask wearing. Gate Agent also made additional PAs prior to pushback. Throughout the flight; passengers would not comply with mandate. Notified Dispatch.




Synopsis: Air carrier First Officer reported that despite multiple PAs; passengers would not comply with face mask policy.
Date: 201910
Local time of day: 1201-1800
Location: DFW.Airport, TX
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing; Taxi
ATC / advisory: Ground DFW
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Communication Breakdown; Confusion
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Procedure; Human Factors; Airport; Chart Or Publication; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: I landed Runway 17C and was given taxi instructions to taxi via M; EL to hold short Runway 17R. With setting sun I confused Runway 17R and the taxiway. As we rolled up to the hold short line the First Officer yelled 'hold short.' At that point; I realized I confused the runway and taxiway in front of me. I rolled beyond the hold short line; coming to a stop. Tower canceled takeoff clearance for a departing aircraft and cleared us to cross Runway 17R.


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


Synopsis: A320 Captain reported confusion and a loss of situational awareness that resulted in a runway incursion.
Date: 201511
Local time of day: 1801-2400
Location: HWD.Airport, CA
Flight conditions: VMC
Light: Night
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Banner Tow
Flight phase: Landing
Airspace: Class D HWD
ATC / advisory: Tower HWD
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airport; Airspace Structure; Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X was conducting a banner drop operation. I approved the Banner drop operation. We had a crosswind of about 060 degrees at 6 knots. As Aircraft X dropped the banner and started to climb upwind; Aircraft Y requested a right crosswind departure off of Runway 28R. I cleared Aircraft Y for takeoff. Aircraft X requested to land on Runway 10R because of the crosswind. I advised Aircraft X as he was downwind to make a 180 degree turn and make right traffic for Runway 10R. Aircraft X acknowledged and made a 180 degree turn and an unauthorized short approach at the approach end of Runway 10R. Aircraft Y was still on Runway 28R; so I instructed Aircraft Y to cancel take off clearance; hold position; Aircraft Y did not acknowledge and began rolling. Aircraft X was short final and almost touching down as Aircraft Y became airborne. Simultaneous opposite direction may have occurred as Aircraft Y departed and Aircraft X landed. I would recommend clarification on the rule of Simultaneous Opposite Direction Separation.




Synopsis: Local Controller reported that an aircraft departed at the same time as an aircraft was landing on a parallel runway in the opposite direction. Contributing was the landing aircraft making an unanticipated short approach and the departing aircraft not acknowledging their takeoff clearance being cancelled.
Date: 201204
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: A310
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Aircraft component: Escape Slide
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Situational Awareness; Communication Breakdown; Distraction; Fatigue; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Company Policy; Staffing; Procedure; Human Factors
Primary problem: Ambiguous

Narrative: Long night; complications with transportation to the airport; fuel spill; late departure from origin; late arrival at destination; continual late stairs to the airplane at destination; habitual late ACARS not closing because of main cabin door not being 'cracked' enough.  Upon block-in; stairs had been late getting to the airplane during the week (as late as 13 minutes); ACARS was not closing out unless doors were 'cracked' open more than normal; etc.  Shutdown was normal and checklists accomplished.  While waiting for stairs; Captain cracked the door to initiate ACARS closing process; but door was not disarmed.  Door starting initiating process of opening and inflating slide.  Slide never deployed completely nor door opened all the way.  Slide and door remained partially deployed and open.  No injuries; no damage except for need of slide replacement.  Log book entry made.  Normal checklist flow and normal procedures dictate that after block-in; the First Officer or crew insure that the slides are disarmed.  Because of aforementioned distractions with late stairs; etc.; the doors were not double checked via normal procedures.  Thus; any crewmember must insure that the door is disarmed completely before opening the door for any reason.




Synopsis: An A310 Captain opened the main cabin door before disarming the slide because he was impatient about ground crew delays and ACARS close-out message sending; and so partially inflated the slide.
Date: 202001
Local time of day: 1201-1800
Location: LAX.Airport, CA
Flight conditions: Marginal
Aircraft: Widebody; Low Wing; 3 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
Airspace: Class B LAX
ATC / advisory: TRACON SCT
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Distraction
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: 7 mile finale on glide slope between Hunda and Limma; a drone flew overhead.  Reported to tower; landed as normal.  Unannounced drone traffic. Drone procedures made more aware to public.




Synopsis: Pilot reported a NMAC with a drone on final into LAX Runway 25L.
Date: 201308
Local time of day: 1201-1800
Location: LGA.Airport, NY
Flight conditions: Marginal
Aircraft: B717 (Formerly MD-95)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower LGA
Aircraft component: Antiskid System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Gate Agent / CSR
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The First Officer was landing on Runway 22 at LGA. The approach was normal; touchdown was normal as was the rollout. Brake application was normal throughout the landing rollout. Exiting the runway the ANTISKID R FAIL alert illuminates on the EAD. Upon arrival at the gate we discovered the Number 4 tire had deflated. We wrote the airplane up which resulted in a cancellation. This event was possibly caused by the Number 4 brake locking up. This airplane had previously been written up for the same occurrence at LGA.




Synopsis: B717 Captain reports an ANTISKID R FAIL alert exiting the runway after landing. Upon gate arrival the number four tire is found to be deflated. The aircraft had previously experienced the same fault/failure sequence.
Date: 201706
Local time of day: 0601-1200
Location: SNA.Tower, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class C SNA
ATC / advisory: Tower SNA
Second aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Distraction; Training / Qualification
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; 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 New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Manuals; Airspace Structure; Chart Or Publication; Company Policy; Procedure
Primary problem: Procedure

Narrative: Aircraft X was on a 3 mile final and was cleared to land Runway 20R. Aircraft Y was on the landing roll and was instructed to turn left on taxiway Delta and then contact ground. There was no read back of instructions from Aircraft Y. Ground Control had coordinated to cross Runway 20R at Delta with a jet and was blocking taxiway Delta. Aircraft Z was on an IFR departure that was instructed to cross Runway 20R at Lima and fly Runway Heading from Runway 20L at Kilo. At this time I noticed that Aircraft Y was turning right at taxiway Delta. Since he was not going to be clear of the runway; I issued Aircraft X a go-around.Per our LOA with SCT; a heading of 195 with a climb to 3;000 ft was issued to Aircraft X. This would put Aircraft X in conflict with Aircraft Z who was flying runway heading and was less than a mile on the upwind. To avoid an imminent loss of separation; I issued an immediate turn to a heading of 150 to Aircraft Z. Traffic calls were issued to Aircraft X. In trying to avoid an imminent collision as well as a loss of separation; I gave a vector (heading 150) to Aircraft Z; which was below the MVA. The MVA is 1;900 ft and Aircraft Z was climbing out of 1;100 ft.Hindsight is 20/20 but in retrospect; I should have realized that I could have issued Aircraft X an immediate turn to 215 since there was a change to our LOA with SCT.




Synopsis: SNA Tower Controller reported issuing a turn to a departing aircraft beneath the MVA to avoid confliction with another aircraft going around.
Date: 201302
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Weather elements / visibility: Icing
Light: Night
Aircraft: B737-800
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: Pitot/Static Ice System
Component problem: Design; Malfunctioning
Reporter organization: Air Carrier
Human factors: Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Took Evasive Action; Flight Crew FLC complied w / Automation / Advisory; General Maintenance Action
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: During cruise flight at FL370 Captain's airspeed and altitude disagree indicators illuminated followed by EEC failure to soft mode. Suspected pitot blockage from icing; followed Unreliable Airspeed checklist and EEC procedure in QRH and began descent to FL270. Passing through FL290 all indications returned to normal and remained that way for duration of flight.

Callback: The reporter stated that at the time of this event; they were IMC just in the tops of clouds. He stated that the first few minutes of this event were exciting but after the descent was in progress things returned to normal. This event was the third time the Captain's pitot system was unable to prevent ice accumulation so Maintenance replaced the pitot system which corrected the failing.



Synopsis: A B737-800 Captain pitot tube failed to prevent ice accumulation at FL370 resulting in the Captain's Altitude and Airspeed disagree and EEC failure to soft mode. The pitot system was replaced after this event and the third maintenance log entry.