elihoole/asrs-aviation-reports huggingface dataset:
Date: 202001
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Galley Furnishing
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Aircraft; Company Policy; Procedure
Primary problem: Company Policy

Narrative: I am submitting the report because this instance/issue needs a lot of attention.Forward catering happened during boarding. The previous crew filled up both carts with garbage at the bottom after consolidating; as we are supposed to do. I watched catering take out the trash and dirty trays; and put the clean glasses in that same cart and load it back for me. Guests were able to see this just as clearly as me.But this raises much bigger questions. Is this normal practice? [We were] told that all carts are deep cleaned before being re-loaded on a flight. Obviously not today. Also with the corona virus spreading internationally; this promotes the spread of the disease. Should I have stopped the operation and maybe caused a possible further 1 hour delay to wait for catering to bring me 'hopefully a clean cart'? If they are doing this while loading most likely it's a standard practice.Catering should not switch things out of the carts. It should all [be] loaded and changed out at the kitchen.Catering should not put clean dishes or food in a previously dirty cart that had trash bags full of trash without being washed out.Catering should be better supported so that they don't cut corners like that.




Synopsis: Flight Attendant reported that a catering cart was used to transport trash and dirty trays and was not cleaned before being loaded with clean dishes and food.
Date: 201303
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: I was returning to destination airport; and conditions on DUATS (approximately one hour prior) indicated a 5;000 FT ceiling with 6 miles visibility and winds 170 degrees at 11 KTS; and I remained VFR throughout the flight. I had expected to land with a headwind but was sent to Runway 22L with a crosswind almost perpendicular to the runway. With 10 degrees of flaps and the power at idle; I intended to touch down with the left gear (due to the crosswind from the left) and continue to touch the right then the nose gear. Upon touching the left gear down I believe I experienced a gust from the left which caused the tire to jump off of the rim and the rim struck the runway. The plane proceeded to balloon off of the runway and then touch again; except on the rim instead of the tire. I reacted to the unusual situation and tried to settle the plane on the runway as it began to a wave pattern. After striking the runway a total of two times; the plane settled on the third and I applied full brakes and continued to taxi a short distance to the taxiway at the end of [Runway] 22L. When I observed the plane was not fit to taxi any further; I called the Tower for assistance and shut down the engine; except for the necessary lights. Upon getting out and inspecting the plane visually I observed the left tire hanging off of the rim; the prop had struck the runway and was bent at the last 1.5' on each side and the front gear appeared damaged. Fire rescue arrived and assisted in putting the left gear on a skid and a tug towed the plane to the maintenance hangar. My judgment or performance was never affected by any substances or lack of sleep and I had full mental capacity. The aircraft was rented.




Synopsis: Cessna 172 pilot experienced a crosswind landing where the left tire departed the wheel.
Date: 202002
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Ground Personnel
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: I observed a cargo transport; known as a 'Bobcat' towing 4 LD7 dollies loaded with containers as an aircraft was pulling into a gate. The Bobcat traveled from aircraft left to aircraft right in front of the aircraft without any sign of stopping or acknowledging the aircraft's presence. I observed the aircraft lurch forward as if the pilot had to make an emergency braking maneuver in order to prevent collision with ground equipment. The Bobcat driver did not give way to a live flight. The truck was operated by a local vendor. I immediately reported the incident to the Ramp Tower but may have reported the wrong truck number.




Synopsis: A Ramp worker reported a vehicle drove in front of a taxiing aircraft causing the aircraft to abruptly stop.
Date: 201512
Local time of day: 0001-0600
Location: ZMP.ARTCC, MN
Aircraft: Medium Transport
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZMP
ATC / advisory: Center ZMP
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft was handed off to me at 41;000 feet with a pilot's discretion descent to 35;000 feet. I had faster traffic behind them at 34;000 feet that I needed to get them underneath; so I gave them descent to 24;000 feet to get them under my traffic and they were only 100 miles from their destination. The pilot's response was unable. So I told them I have traffic and [they] need to descend; they responded that they could not for operational reasons. They would not take a descent until 60 miles from their destination. With the amount of enroute traffic in the area it makes the workload for the controller much more difficult because they refuse to take an ATC clearance. This same aircraft does the same thing every time they come into our airspace. Every time it's a struggle to get them to take a clearance to clear traffic as they say they can't do it. It doesn't matter what our traffic is they will not take a clearance.The pilot of this aircraft needs to be talked to about the situation that he creates every time he flies through. This creates a dangerous situation every time he comes through.




Synopsis: An aircraft refused descent clearance from ATC. The reporter states this aircraft routinely refuses descent clearances.
Date: 201309
Local time of day: 1201-1800
Location: ELP.Airport, TX
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ELP
Reporter organization: Air Carrier
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Chart Or Publication; Human Factors; Procedure
Primary problem: Human Factors

Narrative: TWR ISSUED TAXI INSTRUCTONS TO TAXI TO RWY 8R VIA THE RAMP AND TAXIWAY KILO.  NEITHER PILOT RECALLS ANY HOLD SHORT INSTRUCTIONS.  WHEN WE TURNED LEFT ON TAXIWAY KILO AS DIRECTED IT IMMEDIATELY INTESECTED TAXIWAY ECHO WHICH HAPPENS TO BE ON THE EXTENDED CENTERLINE OF RUNWAY 8R.  WHEN WE TAXIED ON TO ECHO THE TOWER CONTROLER POLITELY ASKED US TO 'IN THE FUTURE HOLD SHORT OF ECHO UNTIL CLEARED ON TO IT'   WE DO HAVE AN AIRPORT DIAGRAM WHICH STATES THAT YOU ARE NOT TO TAXI ON TO TAXIWAY ECHO IF TOLD TO HOLD SHORT OF THE RUNWAY. WE WERE NOT TOLD TO HOLD SHORT. THERE WAS NO TRAFFIC CONFLICT. SUGGEST CLARIFYING WITH ATC. IDEALLY ATC SHOULD INFORM YOU TO HOLD SHORT OF TAXIWAY ECHO AT KILO IF THAT IS WHAT IS EXPECTED.




Synopsis: Air Carrier pilot reports being inadvertently crossing Taxiway E without clearance to do so. The reporter does not believe a hold short clearance was issued by the Tower; although this taxiway is an extension of Runway 8R and treated as part of the runway by the Tower.
Date: 202009
Location: ZZZ.Airport, US
Aircraft: Skyhawk 172/Cutlass 172
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During landing aircraft started to porpoise I tried to hold off nose gear but prop blade struck the runway.




Synopsis: C72 Pilot reported loss of control on landing resulting in prop strike.
Date: 202011
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other All
Airspace: Class A ZZZ
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Procedure; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: As the flight progressed; I was made aware that two particular passengers; seated XX5 and XX6; were repeatedly not in compliance with the mask policy.  I made the announcement encouraging everyone to wear their masks.  Subsequently; the passengers XX5 and XX6; failed to comply and attempted to use 'Active eating and drinking' as an excuse not to wear the mask.  The purser advised me that they were non-compliant for most of the X+ hour flight; so I forwarded their names and seat numbers to Dispatch to support the flight attendants and to document the passengers' non-compliance so that company can evaluate whether they be allowed future travel.  The customers were met by Customer Service representatives upon arrival in ZZZ.




Synopsis: Air carrier Captain reported two passengers were not complaint with face mask policy during flight.
Date: 202107
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Dispatch
When detected: Other Arrival gate
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: In weight and balance data; no dry ice was listed. Arrival airport Ramp called Name and told him that there were approximately 44 kg of dry ice in 2L due to [medical supplies]; but no listing as such.


Second narrative: Notified by Operations Control that 44 lbs of dry ice was on our airplane in position 2L. Had two packs and no pneumatic MEL's.  Dry ice limits not exceeded. HAZMAT paper work stated ' no DG on board'. Continued safely to destination.


Synopsis: Air Carrier Captain and Dispatcher reported undocumented transport of hazmat due to a communications breakdown between Dispatch and departure Load Control.
Date: 201305
Local time of day: 1201-1800
Location: ZAU.ARTCC, IL
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZAU
ATC / advisory: Center ZAU
Second aircraft: Embraer Jet Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Human-Machine Interface
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings; Procedure; Human Factors
Primary problem: Human Factors

Narrative: A CRJ2 was assigned FL230 230; DEBAR3 to CVG. ERAM auto flashed the CRJ2 about 15 miles north of FWA; (40-ish miles from the ZAU-ZID boundary). The ZAU/ZID LOA requires CVG arrivals to be at or above FL210. My D-Side trainee called MIE sector and coordinated that the CRJ2 would descend when clear of traffic. That traffic was an ERJ; WATSN1 to ORD at FL220; head on with the CRJ2. We had just received communications from MIE; the ERJ was still in MIE's airspace; and the CRJ2 was still well inside our airspace; still on our frequency. MIE amended the data block; without control; still in our airspace; to show an altitude of FL210. The CRJ2 was at FL230; with opposite direction traffic at 12 o'clock and 10 miles at FL220. The MIE Controller could have used a local interim altitude; but it is never appropriate to amend a data block in another Controller's airspace; where you do not have control and are not communicating with the aircraft. I believe that would violate the requirement that the data block reflect what the aircraft is doing. I believe both facilities should fall back to HOST until clarification about proper data block coordination is completed and ZID controllers retrained on ERAM and 4th line usage.




Synopsis: ZAU Controller described an unsafe event when an adjacent Controller amended data block information not under hiS control.
Date: 201309
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Trailing Edge Flap
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew FLC complied w / Automation / Advisory; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was flying the airplane to a normal ILS. I called for Flaps 9 and we got a flap fail message. We ran the appropriate checklists and continued with a no flap landing. We had the tower roll the emergency equipment as a precaution. Taxied to the gate as normal. Called Maintenance. Everything was normal; other than the flaps being at zero when we landed.




Synopsis: An EMB-145 CAS alerted FLAPS FAIL when Flaps 9 selected so the Checklist was completed; an emergency declared and an uneventful flaps up landing followed.
Date: 201907
Local time of day: 0001-0600
Location: ELP.Airport, TX
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp ELP
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: Distraction; Situational Awareness; Troubleshooting
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: On taxi in to Gate XX in ELP; we were on the taxi line rounding the corner from Taxiway G into the alley. We noticed that the (other carrier) aircraft parked (shutdown with the jetway attached) at Gate XXY was far back from the normal parked position.  It appeared as if we did not have enough wingtip clearance to stay on the centerline so we deviated left quite a ways to safely avoid the parked aircraft. After parking at Gate XX; with no incident; I asked the Ops Agent if they knew of any Crew advisories/complaints concerning what I thought was a hazardous parking position for (other carrier) aircraft. Agent said they did not know of any such concerns. I noticed that the (other carrier) aircraft jetway was telescoped out to its fullest extension; which looked unusual. It was (time) at the end of a long day so this very well could have been a visual illusion; but I thought I would [report it] anyway.I think we should look into whether there is actually enough clearance for us to safely taxi around the (other carrier) aircraft at Gate XXY while on the painted centerline or whether we need to issue an advisory to our pilots to plan to deviate left inbound or right outbound.




Synopsis: B737 Captain reported concern whether there is enough taxiway clearance for two aircraft around the corner of Taxiway G going into the alley at ELP airport.
Date: 201901
Local time of day: 0001-0600
Location: PIT.Airport, PA
Flight conditions: IMC
Weather elements / visibility: Snow; Rain; 1/2
Light: Dawn
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground PIT
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During taxi out during active snowfall; we inadvertently crossed a non-standard hold short line for 28C at PIT on taxiway E parallel to the runway centerline.We had originally planned on departing 28R and visibility on ATIS was 9 miles with -SN (light snow); but then was changed to 28C and the visibility dropped to 1/2 mile with mist and SN (moderate snow) during our taxi out. We updated our Takeoff Landing distance and the Captain updated his taxi out brief while we were at the de-ice pad. 'Expecting to get left turn taxiway N; left turn taxiway E to 28C; no hot spots.' After de-icing; we were cleared as expected by Ground. Unfortunately; after we made the left turn on E; I was heads down finishing the before takeoff checklist (checking the weather radar I believe) and the Captain inadvertently taxied slightly (est. 5-10 feet.) past the non-standard hold short line (parallel to the runway; not perpendicular) which was completely obscured with snow. At about the same time; tower cleared us for takeoff and I am sure was unable to see that we had slightly passed the hold short.


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


Synopsis: Flight crew reported incurring a runway incursion at PIT airport due to an unusual placement of hold short line; coupled with low visibility and snow.
Date: 201403
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Cargo Pit Compartment
Reporter organization: Contracted Service
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft; Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Company Policy

Narrative: Contract Technician was called to the gate at ZZZ for panel not installed on Forward Cargo Bulkhead. Technician inspected area and reinstalled self-locking fasteners on panel. Technician returned to FBO and called Air Carrier X Maintenance Control. Air Carrier X Maintenance Control verbally gave Technician the cargo panel install reference and the offer of a fax or e-mail hard copy was never made.  The Technician made the Logbook entry with the verbal reference and returned to the gate. Upon exiting the vehicle; the Technician was met by an FAA Air Carrier PMI Maintenance Inspector. The Inspector asked the Technician where and how he had received the reference for the work performed. Upon answering; the FAA Inspector asked the Technician; if that was a good idea; not to read the Airbus Aircraft Maintenance Manual (AMM) reference for himself. The Technician responded that it was not a good idea and returned to the FBO for an actual copy. Air Carrier X's policy is to not allow Contractor Maintenance to have direct Airbus manual access. The Technician has constantly encountered the problem of requesting AMM / General Maintenance Manual (GMM) hard copies before performing maintenance actions. This problem has been brought up several times by the Technician to Air Carrier X's Maintenance Control and to his superiors; including his Lead and Director of Maintenance (DOM). Proper access to Airbus and Air Carrier manuals has caused Contract Maintenance compliancy [issues]. The Contract Maintenance personnel would also like the ability to research any questions they may have while performing their duties.




Synopsis: A Contract Aircraft Maintenance Technician (AMT) reports about the constant problem of having to request Aircraft Maintenance Manual (AMM) and General Manual (GM) hard copies prior to performing maintenance actions on an Air Carrier's aircraft.