elihoole/asrs-aviation-reports huggingface dataset:
Date: 201409
Local time of day: 1201-1800
Location: EWR.Airport, NJ
Light: Daylight
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower EWR
Second aircraft: Widebody; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Trainee; Local
Reporter qualification: Air Traffic Control Developmental
Human factors: Communication Breakdown; Situational Awareness; Distraction; Confusion
Anomaly: ATC Issue 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 Separated Traffic
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X was landing Rwy XX and an Aircraft Y was landing Rwy YR.  We had LAHSO winds for XX but not for YR. Even with early speed adjustments; these two aircraft were tied to the airport; so I planned to send the Aircraft X around.  One of the supervisors asked why I wasn't issuing a LAHSO clearance to Aircraft X; and I said I couldn't because Aircraft Y was a foreign carrier that did not participate in LAHSO.  She said that only meant that the Aircraft Y couldn't hold short; but I told her that I was taught that foreign carriers could not be involved in any operation in which LAHSO was being conducted.  She then went to my FLM to get his opinion and he concurred with the other supervisor (but I think there was some differences of opinion by other controllers in the Tower as to how this rule is interpreted); so I begrudgingly issued the LAHSO clearance to Aircraft X against my better judgment. When I got home; I checked my SOP; and under LAHSO; Section 1-5-2; procedure 'n'; it states; 'Foreign air carriers (Part 129) cannot participate in LAHSO until approved by the FAA as listed in Appendix P. Note: 'Participate' means that an aircraft cannot be issued a LAHSO instruction nor have another aircraft conducting LAHSO on the intersecting runway.' The misdirection from the supervisor conflicted with EWR's facility directives (regarding LAHSO); which ultimately resulted in an illegal operation (loss of runway separation).Supervisors and all tower team members must be familiar with facility directives; especially with regard to ATC separation requirements.




Synopsis: EWR Local Controller reports of two aircraft that are tied for the airport.  He decides to send one around and the FLM questions; why he isn't using a LAHSO.  Controller states it is illegal because one is a foreign carrier.  FLM advises it isn't true.  Controller then has aircraft land; and later finds out that it was an illegal operation.
Date: 202009
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Pilots [are] not wearing masks when flight attendants are in the flight deck. Captain leaves [the] flight deck without mask on.




Synopsis: Flight Attendant reported that when flight attendants are in the flight deck; pilots do not wear face masks.
Date: 201704
Local time of day: 1201-1800
Location: SEA.Airport, WA
Flight conditions: IMC
Light: Daylight
Aircraft: Medium Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B SEA
ATC / advisory: Tower SEA
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: ATC Issue All Types; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: Encountered wake turbulence on final to ILS 16R 1nm prior to FINKA. Ceilings 2500 broken. Broke out of clouds on ILS glidepath and encountered wake turbulence from preceding 737. Wings rolled 15 degrees to left and right and required additional power to maintain airspeed. Flew above glideslope and no further encounter happened. No wake turbulence advisory from ATC. Numerous traffic shown in front of us on MFD for both 16L and 16R.ATC should adhere to wake turbulence separation into Seattle despite high demand times for safety. If ceilings are low; advise aircraft in IMC they are following aircraft ahead so pilots can take corrective action for wake avoidance.




Synopsis: Air carrier First Officer reported encountering wake turbulence on final to SEA Runway 16R in trail of a B737.
Date: 201303
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During descent on the arrival; autopilot disconnected; AC Crosstie Lockout; Left Generator OFF; and L AC Bus OFF illuminated. Due to high workload of EMG/Abnormal procedure and close proximity of the airport; an emergency was declared. Captain was flying the airplane and continued to fly the airplane; while First Officer accomplished as much of QRH procedure as possible before landing. On Base leg to runway; Captain instructed the First Officer to discontinue QRH and accomplish the normal procedure before landing checklist. We flew a visual approach; landed and taxied to gate.


Second narrative: Left side electrical malfunctions; i.e. AC X tie lockout; left ac bus... Captain [PF] declared emergency to ATC. First Officer accomplished as much of QRH checklist as possible; changed focus to remaining descent and landing checklists. Landed aircraft.


Synopsis: MD80 flight crew experienced an AC Crosstie Lockout; Left Generator OFF; and L AC Bus OFF indications during descent for landing. An emergency is declared and as much of the QRH procedure as possible for the failure is accomplished prior to landing.
Date: 202005
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Training / Qualification; Distraction
Anomaly: Deviation - Altitude Undershoot
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Working ZZZ Center I believe; at FL380; was given instructions to cross ZZZZZ at FL290. Set 500 FPM descent in FMS; with intention of verifying and adjusting once stabilized in descent. Person A came from cabin and began conversation at cockpit; distracting me from my intended task; and I did not see that we were not going to make 29;000 at ZZZZZ until just before crossing; increased rate of descent in attempt to make [the] restriction. Estimate missing crossing by 500 feet or possibly more; as at approximately the same time; Center called and gave us descent to FL240; so we continued our descent. No mention was made by ATC of any conflict nor any questioning as to what our status for making the restriction was. This was our first trip in the aircraft in almost three months; due to COVID-19 pandemic issues; and also the first time we had worked as a crew in almost three months. Recent experience was certainly a factor; but not an excuse. I am extremely disappointed with myself for not staying better focused on my immediate task; and counseled the FO on duty to monitor when Pilot Not Flying.Suggest all crews redouble efforts and vigilance in these trying times as we are all working in unfamiliar situations now with the pressures put on us by the pandemic. Fortunately at this early stage of things moving back toward some semblance of normal; there was probably not a great possibility of a traffic conflict. That will change in the coming days; and even though we may not personally make any more mistakes as these; there will be other crews coming back to flying from furloughs; etc. that still need to get their game back. Looking out for ourselves and the other guys and gals even more than we did before will be the new normal for some time.




Synopsis: Corporate Captain reported experiencing an undershoot of a crossing restriction and cited lack of recent flying experience due to the COVID-19 pandemic as a contributing factor.
Date: 201906
Local time of day: 0001-0600
Aircraft: EMB ERJ 140 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight; Routine Inspection
Result: General Maintenance Action; General Work Refused
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Ramp crew provided a [Load Report] which indicated 104lbs of freight. FO (First Officer) stated that while doing his preflight walk around he noticed that the cargo was human tissue. The [Load Report] did not indicate the cargo was anything more than freight. The [Load Report] also did not indicate that it was a UN3373. Captain went to baggage compartment and checked the packages for any labels. There were no UN3373 labels on the package or any other hazardous materials markings or labels seen; there was; however; a large bright label that stated 'TISSUE UNDER QUARANTINE: NOT YET DETERMINED SUITABLE FOR TRANSPORTATION IN ITS CURRENT FORM'. After not seeing an appropriate UN3373 label and seeing a label expressly stating that the package may not be safe for transportation; the Captain refused the package. The ground crew complied with the Captain's instructions and were very cooperative. The Captain contacted the Chief Pilot to discuss the issue with him. There were no further issues.The FO mentioned seeing the human tissue cargo to the captain. After noticing that biological material was not annotated on the [Load Report] the Captain checked the cargo himself to ensure compliance.Biological material was loaded on to the aircraft without being appropriately documented or vetted. While a NOTOC (Notice to Captain) is only required if biological material contains dry ice; that biological material must still be labeled properly and be indicated on the [Load Report] as UN3373. Without these labels there is no way to determine if the biological material is acceptable to carry. Neither an appropriate UN3373 label nor [Load Report] indication were used.The biological material was removed from the aircraft.Better training on appropriate Hazmat markings; labels; notification; and acceptance.




Synopsis: EMB-145 First Officer reported Hazmat cargo labeled not suitable for air transport in cargo compartment. Package removed prior to departure.
Date: 201701
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuel Tank
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Passing 18;000 on climbout noticed an unexplained decrease in right outer fuel quantity. Followed QRH procedures for fuel feed manual control and fuel leak. Did not confirm a fuel leak but right outer quantity continued to decrease. Right outer [fuel quantity] should not have burned down at all. After completing fuel feed manual control with center pumps off to ensure fuel was burning from inner tanks right outer continued to decrease. Entered fuel leak checklist and did not confirm a fuel leak because only indication was an imbalance but fuel total continued to burn down on pace with flight plan release. Consulted with [Maintenance] and Airbus tech pilot. Diverted to nearest airport. Aircraft landed exceeding outer wing tank limits; no problems noted. On the ground with engines shutdown and no fuel pumps on; right outer continued to decrease quantity over a one hour period.


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


Synopsis: A300 flight crew reported an unexplained decrease in right outer fuel quantity and diverted.
Date: 201212
Local time of day: 1801-2400
Location: MHV.Airport, CA
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Final Approach
Airspace: Class E E10
ATC / advisory: TRACON E10
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Approach cleared Air Carrier X to 9;000 FT. At seven mile ATC tells Air Carrier X report the visual approach. Air Carrier X contacted CTAF Unicom frequency. Transmitting our position from the field. Unicom replied with field conditions. Air Carrier X then switched back to Approach Control requesting lower. ATC then cleared Air Carrier X to 7;000 FT. At five miles we keyed up the lights. I requested lower; Approach Control said unable due to protected air space. What protected Airspace? I reported the field in sight expecting to hear cleared for the visual approach. Due to our close proximity and 7;000 FT altitude and mountains we continued to the field joining the glide path. I wanted to stay in my protected airspace as the Approach Control was busy with another aircraft. On our visual descent; and after calling the field; Approach Control asked our altitude. I replied we have the field descending on glide path. Approach Control replied 'maintain your altitude!' We leveled around 4;800 FT. He again said he couldn't clear us below 7;000 FT. Air Carrier X requested Approach to tell us when clear of said airspace. Approach replied one mile. So we're now 4;800 FT one mile from the end of the runway. Air Carrier X was in no position the do a stabilized approach so we executed a missed approach. Being so confused by Approach's inability to communicate he needed us to cancel our IFR clearance in order for us to descend; we canceled our IFR clearance and did a circle to land to Runway 30 at MHV.




Synopsis: Air Carrier on a Visual Approach to MHV was restricted by ATC at an altitude that required a go around. The restriction to clear other unknown airspace.
Date: 201909
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Aircraft component: Communication Systems
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Dispatcher
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
When detected: Aircraft In Service At Gate
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Ongoing issues with communications; while using IPICS; between the RTC and flight crews/Supertug. RTC performed a radio check with the flight crew after switching from the main to the standby radio on IPICS. The crew did not respond to the RTC communication on the first call; but responded on the second call stating that they had replied; but the RTC did not hear. 5th occurrence of the morning. The RTC switched to the telex system shortly after this incident.




Synopsis: Dispatcher reported difficulty communicating with a flight crew during preflight.
Date: 201703
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Captain; Pilot Not Flying
Anomaly: Flight Deck / Cabin / Aircraft Event Passenger Electronic Device; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Passenger
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: FA reported that a first class passenger reported to them that his portable battery was heating up and smelled like burning plastic. FA put the battery in a container with water as per their procedure and notified us that they had done that and there was no irregularities at this time. We advised them to carry on with their procedures and monitor the battery. Advised dispatch of the situation as well.Looking into if this particular type of battery pack is good for flight.Make: UnidenModel: WM4807


Second narrative: While cruising at FL350; we got a call from a flight attendant.  Flight attendant informed us that a passenger handed a phone charging battery pack that smelled like 'burnt plastic.'  Flight attendant said that the pack was not hot to the touch when the passenger handed it to her; but it did have a smoky smell.  The FAs followed the FAM procedure for Lithium battery fires that say to submerge the device in water.  When we got the call they already completed this procedure and there was no further sign of smoke or fire.  Therefore; I decided that declaring an emergency would not be needed in this case.  Instead; we continued the flight with caution; monitoring the condition of the battery pack.We verified that the flight attendant's manual procedures where complied with; notified dispatch and asked the FAs to keep monitoring the condition of the battery pack.The passenger was charging his phone with the device while this happened.  It was not connected to the PC outlet.


Synopsis: EMB-175 flight crew reported a passenger's portable battery overheated so the Flight Attendant placed the battery in a water container as per company procedure.
Date: 201601
Local time of day: 0601-1200
Location: EWR.Airport, NJ
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower EWR
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While landing in EWR LOC 22R the Captain landed on the displaced threshold area prior to the 22R threshold of the runway. At 200 feet I told him he could not land in the displaced threshold area; and he ignored my statement. I repeated myself several times explaining this was prior to the landing area of 22R. He ignored me and continued his approach and landing on 22R. He landed approximately 100 feet before the threshold of 22R; ignoring the displaced threshold markings. He asked what I was saying on short approach and when I explained the displaced threshold; he blew me off stating haven't you ever landed on that before.The Captain had total disregard for his FO; and the rules about landing in a displaced threshold area.




Synopsis: A320 FO reported the Captain landed on the displaced threshold of Runway 22R at EWR even after the FO warned against that.
Date: 201810
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: 6
Light: Dawn
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: VFR
Mission: Passenger
Flight phase: Taxi
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Observer
When detected: Taxi
Result: Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While taxiing into position on [the] runway; another aircraft reported flames coming out of our Number 1 engine. We taxied clear; shut down the engine; informed the Flight Attendants; and returned to the gate.




Synopsis: B737-700 Captain reported returning to the gate after another aircraft reported flames coming from the Number 1 engine during taxi.