elihoole/asrs-aviation-reports huggingface dataset:
Date: 201704
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Distraction
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Company Policy; Human Factors
Primary problem: Human Factors

Narrative: The flight was slightly delayed for maintenance at gate when ready for push. When door reclosed and announcements repeated was doing compliance check for cabin secure. Passenger was in emergency exit row. You would think exit row passenger of all passenger would be willing and able to comply with crew instructions. This man should never be allowed to sit in an exit seat again! At the time of walk through his seatbelt was undone was under his feet in aisle and newspaper was under his feet. I requested he stow bag and laptop and fasten seatbelt and asked if newspaper was trash could I take it for him. He said no he was reading it so I asked him to remove it from floor in exit row so no one would get hurt if we actually had to use exit; then I continued down aisle. On passing him on my way back he still had not complied with one thing I said. I seriously thought about removing him from exit seat; but did not want to escalate situation. So I made the same request AGAIN. He told me he was keeping his laptop on his lap because he could. I was wrong. I then informed him that I was not wrong and that it was in my manual as such and I would be happy to show him. Finally he said I will put it away but you are wrong and then told to LEAVE HIM ALONE. I talked to the CA of the situation. CA told me to show him in magazine where it is required to stow laptops. I didn't because as I said it would have escalated. This sort of behavior is unacceptable in exit row passenger. This man was of course one of the airline's [high] mile passenger. It is a shame because they hold a status that we cannot do our jobs. Something truly needs to be done. Our hands seemed to be tied and I have a plane full of passenger to protect. When these passenger disobey federal regulations there should be repercussions.




Synopsis: CRJ-200 Flight Attendant reported a passenger in an emergency exit row was defiant and non-compliant when asked to stow his laptop and remove newspapers from the exit row floor beneath his feet.
Date: 202104
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Taxi
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Commercial Fixed Wing
Reporter organization: Personal
Reporter function: Captain; Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Distraction
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Chain of events. ZZZ Ground cleared me to taxi from FBO. 'Taxi to Runway XX via Taxiway 1; Taxiway 2; Taxiway 3; cross Runway XY.' On Taxiway 3; approaching Runway YX/XY; I was looking down at my checklist; when I looked up; I was startled to see a regional jet on relatively short (1 mile?) final for Runway YX. After I crossed XY/XY; the regional jet landed without incident.Human Performance Considerations. First; when taxiing; one needs to be focused outside the airplane. When approaching a runway; slow to look for landing/departing traffic. If I had seen the regional jet earlier; I may have either increased taxi speed; determined no speed change was required or called Ground and advised that I would wait for landing traffic.With the pandemic; until recently; commercial air travel has been significantly reduced. Tower personnel may have been reduced as well. I believe one Controller was handling Ground and Tower. With activity picking up; ATC needs to be staffed appropriately as well.




Synopsis: GA pilot reported a conflict after being told to cross a runway; and while crossing observed an aircraft on short final. Pilot cited distraction and ATC staffing as contributing factors.
Date: 202009
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
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 Passenger Misconduct
Detector: Person Flight Attendant
When detected: Taxi; Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Human Factors

Narrative: During taxi out; passenger wouldn't put his seatbelt on.  His Mom told me to 'Force him to put it on.' I declined.  The Dad and Mom both attempted to put seatbelt on their son; but no success.  He screamed and refused all of the way out to runway.  I asked the Mom 'How old is your son'?  She told me that he was 4 years old.  I then told her that he also has to wear a face mask.  Her response was; 'Good luck with that.' Another Flight Attendant also tried to get compliance from them; no luck as well.  I called the CA to inform him.  The other FA informed the Mom that we were going to have to return to gate; and remove them.  We returned to gate; and [they] deplaned.




Synopsis: Flight Attendant reported a child would not wear a seatbelt; nor a face mask and was eventually deplaned.
Date: 201709
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: Mixed
Light: Daylight
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Aircraft Auto Temperature System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climbout; cabin temperature began climbing [and] we were unable to control temperature. All zone temperature indicators eventually read 99 with actual conditions well above. Aircraft side panels were boiling hot. No EICAS messages displayed. Contacted maintenance control for assistance in trouble shooting situation - USELESS. Unable to control temperature and concerned about the extreme heat decided to divert to [an alternate airport].




Synopsis: B767 Captain reported diverting to an alternate airport after the cabin temperature rose to dangerously high levels and could not be controlled.
Date: 201309
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Powerplant Fuel System
Component problem: Improperly Operated
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Human-Machine Interface; Other / Unknown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: The student and I conducted a complete pre flight of the aircraft and all procedures appeared normal. However; upon sumping the engine sump for fuel; the butterfly clip may have gotten stuck on the cowling. However this was easily overlooked as no more fuel was spilling from the sump. Normal startup; taxi and runup procedures were performed and no abnormalities occurred. Upon takeoff total power loss was encountered at about 50 FT AGL. I; the Instructor; immediately took over and safely landed the aircraft on grass inside airport property. No damage was inflicted on the aircraft; airport property; or beings during the event. The cause of the power loss is still unknown; however I can say I learned a valuable lesson. A thorough preflight is key to a safe flight. Checking ALL engine components is required and cannot be overlooked.




Synopsis: PA28 Instructor Pilot experiences a power failure at 50 FT AGL with the student at the controls. The Instructor takes control and successfully lands on airport property with no damage to airport or aircraft. Fuel starvation is suspected.
Date: 202202
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: clear; 10
Aircraft: PA-18/19 Super Cub
Operator: Government
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
Airspace: Class G ZZZ
Reporter organization: Government
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Situational Awareness
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other Landing
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft bounced at slightly higher speed than normal upon landing. Over correction applied and aircraft left runway.




Synopsis: Pilot of a light single engine aircraft reported a bounced landing at higher than normal speed resulted in a runway excursion.
Date: 201410
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Electronic Flt Bag (EFB)
Component problem: Design
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 Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While I personally approve of Air Carrier X trying to update its IT and giving pilots iPads and the new Jeppesen Pro program; and I understand that the company would like to rid itself of paper charts over time; I do not think the new Ram mount is a good product. I tried several different ways to mount the device and could not find any position it did not interfere with something. First; when it is on the window; not only does it interfere with visibility; but it interferes with the possible need to open the window and the release handle. When the mount is placed on the preferred location on the cabinet door of the storage box; it either interferes with that same handle for the window; the crank for that window; the yoke; or it hits your knee. I feel it is a very unsafe device and should not be used. Under a perfect situation; it may work. But if you have to get the window open in an emergency; or if you have to react suddenly to control inputs such as an engine failure; I feel that Ram mount would be in the way. It may work with some aircraft; but I do not feel it works well with the B-777. It's a hazard.




Synopsis: B777 Captain expressed concern about the design of the iPad mount; stating it interferes with other components.
Date: 201503
Local time of day: 1201-1800
Location: LAS.Airport, NV
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground LAS
Aircraft component: Tablet
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Confusion; Situational Awareness; Distraction; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: Airport; Equipment / Tooling
Primary problem: Ambiguous

Narrative: Cleared to taxi via C; B5; B; G; D to Runway 19L.  Once established on Taxiway B; First Officer (FO) advised he was heads down to load final numbers into FMC for takeoff while I was looking for signs marking Taxiway G.  I passed Taxiway G thinking it was B7; but realized my mistake as I could see no further angled taxiways to my right.  I stopped the aircraft to obtain an amended clearance from Ground Control; and was re-cleared to taxi via B; Z; and D.  This was my 13th trip into LAS this month; with most departures previously operating from Runway 1R.  Prior to gate departure on this flight; I briefed the hot spots and expected runway; but did not brief an expected taxi route as it is unpredictable due to construction.  Although I missed the turn; traffic was not a factor and at no time were we near a runway intersection or in danger of incurring on a runway.Contributing factors were poor or non-existent markings to indicate Taxiway G from Taxiway B; and difficulty in reading the 10-9 airport diagram on my iPad due to bright sunlight conditions.




Synopsis: A B737 Captain taxiing to Runway 19R on Taxiway B at LAS missed Taxiway G thinking it was B7. Reporter cited airport signage and relatively dim iPad in bright light as contributing factors.
Date: 201910
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Icing; 0
Aircraft: Falcon 20FJF/20C/20D/20E/20F
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Contracted Service
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting; Distraction; Time Pressure; Workload
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Diverted
Contributing factors: Aircraft; Weather
Primary problem: Weather

Narrative: On route to our destination ZZZ Airport; we started to accumulate ice at FL270. The Captain proceeded to switch on both Engine anti-ice switches as well as airframe anti-ice. A couple seconds later our left engine began to roll back. About a minute or so after that; the right engine began surging but did not roll back completely. We then [Requested Priority Handling] and asked ATC for help to the nearest suitable airport. We then were cleared to descend to 11;000 ft. I started my descent and tried to keep the right engine turning by keeping a low power setting. Meanwhile; the left engine kept surging so I pulled the left throttle to flight idle. While in the descent the Captain ran the emergency checklist items and handled communications with ATC. ATC then cleared us to descend to 4000 ft. and vectored us for the ILS Runway XX at ZZZ. Passing through 10;000 ft. we noticed that the right engine had stabilized and was able to provide sufficient power for landing while the left engine would also provide sufficient power at a lower power setting. The landing phase was uneventful.




Synopsis: Falcon 20 First Officer reported a dual engine rollback while encountering icing conditions; which required a descent and diversion to the nearest suitable airport.
Date: 202006
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: FBO
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: While providing a sightseeing trip to a friend in order to see a specific home from the air I lost track of my altitude and was at one time 350 feet lower than I should have been. The Tower Controller had approved a descent from 1;500 feet to 1;000 feet in order for me to be able to take some photos. When I noticed my altitude; while trying to provide her a good photo; at 650 feet MSL over the water and at times I estimate 650 feet AGL over the land. I violated 91.119(b) in that; 'Over congested areas; an altitude of 1;000 feet above the highest obstacle within a horizontal radius of 2;000 feet.' To correct; I immediately applied power and climbed back to altitude over the water.At no time was the aircraft in any danger of hitting the ground or do I believe I was 'zooming.' The aircraft never banked more than 15 degrees and only exceeded slightly more than 1G at approximately 90 knots IAS.For me the worst part was not in the violation of FAR 91 regs; but as an experienced CFII and pilot of over XX years and XXXX hours; I lost situational awareness and lost 350 feet of altitude without realizing it. If a student of mine had done this; I would have immediately called his/her attention to it before a 100 feet deviation.A contributing factor was not flying regularly due to the Coronavirus. I was not as proficient as I should have been. Three weeks earlier I had flown a solo warm up flight but obviously this was not enough. In the future I will give myself more proficiency flights and humble myself and fly with another CFI to keep my skill level where it needs to be.




Synopsis: Pilot reported while on a sightseeing trip they went too low; pilot eventually caught the mistake and climbed back to a normal altitude.
Date: 202101
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Flight plan: IFR
Mission: Passenger
Flight phase: Other all
Airspace: Class A ZZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Environment - Non Weather Related; Company Policy; Aircraft
Primary problem: Environment - Non Weather Related

Narrative: I work the #X position regularly on the aircraft. Personal observation of the close proximity in which #Z and #X [Flight Attendants] sit; facing each other; is of grave concern to me; due to COVID-19. While occupying the jump seats at XX; true social distancing isn't possible. Depending on height it can be a challenge to sit without our knees touching or without adjusting our feet under the jump seat. All a non-issue; pre-pandemic.The #X flight attendant does not have a door arming or disarming responsibility. There's no reason for the #X's preflight; inflight; or boarding duties to change. I'm suggesting for safety and health reasons the #X Flight Attendant is temporarily relocated to an unoccupied jump seat at door Y for takeoff and landing.




Synopsis: Flight Attendant reported concerns with the close proximity of occupied jump seats during takeoff and landing.
Date: 201606
Location: ZZZ.Airport, US
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: While taxiing out; Tower informed us that we had a new clearance and to contact Clearance Delivery on our #2 radio and monitor TWR. Just prior to contacting clearance; someone on tower stated revised clearance coming via CPDLC. We received the clearance within seconds of hearing that transmission. We uploaded the new clearance using the load prompt; re-entered the departure rwy; SID; arrival rwy and STAR. However the concern with the procedure is that there appears to be no way of verifying that the new uploaded departure is accurate. When we reviewed the new route we did notice a change to the first fix. However; unlike our procedures at the gate where we verify the clearance against our release there is no way to do this using this procedure when a change comes via CPDLC. Did the fight crew miss something? Or is this an accepted risk that the crews/company are expected to take?




Synopsis: B767 First Officer reported receipt of a revised route clearance via CPDLC during taxi out that was uploaded to the FMC via the load prompt; but was concerned that this procedure did not allow the flight crew time to adequately check the route as they normally done at the gate.