elihoole/asrs-aviation-reports huggingface dataset:
Date: 202010
Local time of day: 1201-1800
Location: ZZZ.Airport, US
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: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Workload; Distraction
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: During boarding as I was walking the cabin to do a compliance check and exit seat briefing a passenger stopped me and questioned why she was seated next to a person she did not know.  I told her I would check and see if there was another seat she could move to.  At this time I did not see any open row that has no other people in it. I was going to send a flight family message to alert the Gate Agent. I walked up a row or two and another lady questioned me about why her seat would not recline (she was in front of the exit row). I explained to her why her seat would not recline and told her I would check with the agent about reseating them.  I then walked to the aft jump seat to send the flight family request. The agent then came down and we had a short conversation about rebooking the one lady and the other passengers who wanted a seat that reclined. There were no other seats to move the recline passenger to and the other passenger was given the option to take a later flight with no guarantee that she would have a seat by herself.  I informed all passengers involved. We took off and it was not till about mid flight that I realized that I had not ok'ed my exit seats. I proceeded right away to the exit row and briefed both passengers and they both were ok to sit in an exit row. The lady passenger did say that she noticed I had not briefed them before the flight. [The cause was] work overload.




Synopsis: Flight Attendant reported inadvertently not briefing exit row passengers due to other passengers making special seating requests.
Date: 202010
Location: ZZZ.Airport, US
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: Situational Awareness; Distraction; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Other Post Flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure; Environment - Non Weather Related; Company Policy
Primary problem: Human Factors

Narrative: We arrived at the airport this morning and headed right to security and over to the X Concourse for departure.  I totally forgot the COVID screening and headed to the gate and off to ZZZ1.It was not until we got to ZZZ1 that I realized the error.




Synopsis: Air carrier First Officer reported forgetting to get screened for COVID-19 prior to reaching the aircraft.
Date: 202009
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dawn
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Military
Flight plan: VFR
Mission: Training
Flight phase: Takeoff / Launch
Aircraft component: Flight Dynamics Navigation and Safety
Component problem: Malfunctioning
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Automation Aircraft Other Automation
Result: General None Reported / Taken
Contributing factors: Aircraft; Procedure
Primary problem: Ambiguous

Narrative: Aircrew got into the seat to launch the aircraft. Normal pre-flight operations; but once crew got link with the aircraft; the chiefs loaded new DLI keys onto the plane without telling any of the aircrew about the new procedures.  This caused over an hour of trouble shooting in order to establish link with the aircraft.  The GCS maintenance guys reloaded the DLI keys into the GCS; but the crew was still unable to establish link with the aircraft again. Aircrew had seen some abnormal readings from the GCS about the aircraft being at [Altitude] when the crew had no link with the aircraft; same with the RPM (108.7) and Uplink sig 1 (112.4%).  The Maintenance crews were able to finally get the correct DLI keys loaded into the aircraft.  Aircrew completed all checklists up to the C-band link test.  At that point the RX2 when checked would send the aircraft lost link.  Aircrew had maintenance swap to a new GDT; which fixed the problem and the C-band link check completed fine.Crew completed the rest of the launch procedures without any problems.  During the taxi out to Runway XX; aircrew started getting  'LOS UPLINK Secondary - LOST' warning.  There were no indications of anything being wrong with the link.  Crew kept an eye on the systems to make sure there wasn't any problems with any of the links.  At the time there was nothing showing that there was anything wrong.Aircrew was cleared to line up and wait on Runway XX.  Once the crew lined up and waited the aircrew got the same warning as before.  The warning did clear; so once the aircrew got clearance to take up the crew did.  Right after the 50 kt. call; the warning came back up.  Pilot decided to continue the take off; but shortly after that; the primary uplink was lost. Sensor called out lost link.  Pilot aborted; sensor responded with abort; abort; abort.  Shortly after sensor reminded the pilot to match settings just in case the aircraft did get airborne.  During this time the crew still had no control of the aircraft.  Aircraft departed the prepared surface.  Aircraft came to a stop after Taxiway X with engine off.




Synopsis: UAV pilot reported the primary uplink was lost causing a remotely controlled aircraft to suffer a runway excursion during takeoff.
Date: 201308
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Dash 8-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON 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 Executed Go Around / Missed Approach; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During approach; approximately 20 NM or 10 minutes out; I noticed that the Number 2 hyd. quantity was at zero; with no associated caution lights. We ran the low hydraulic quantity checklist; which told us to monitor the quantity and pressure in the Number 2 system. On final approach we put the landing gear down; and the gear doors opened; the 3 red unsafe lights were on; and the gear handle was lit. It took much longer than normal for the landing gear to come down. Once down; we had three green and no red lights. We performed a missed approach and did not retract the landing gear. During the missed approach; the Number 2 hydraulic pump caution illuminated. Once level at 2;000 FT.; I called for the Number 2 hydraulic pump checklist; which led us to the emergency landing gear extension checklist. During this time we climbed to 5;000 FT.; declared an emergency; coordinated with Dispatch; our Flight Attendant; and Operations. On final approach the outboard roll spoiler caution light illuminated and during rollout the nose wheel steering caution light also illuminated. After completing all the checklists we landed without incident. Once clear of the active runways we taxied [off the runway]; where Maintenance and a tug met us. Maintenance pinned the landing gear down and we were tugged into gate without incident.




Synopsis: Dash 8 Captain reported loss of Number 2 hydraulic system on approach. Flight crew ran the procedure; contacted appropriate departments; and landed safely.
Date: 201710
Local time of day: 1201-1800
Location: ORD.Airport, IL
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ORD
ATC / advisory: TRACON C90
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: While flying the FYTTE4 RNAV STAR to ORD; we were on downwind leg for Rwy 27R; level at 4000 MSL and between the VULCN and HIMGO waypoints. I and the First Officer (FO) visually acquired a mostly stationary airborne object ahead of the aircraft and to the right side of our flight path. We quickly closed with the object and then the object passed off the right side of the aircraft at very close range. Although I had initially identified the object as looking like some drifting party-type balloons; as we passed the object the FO stated 'I think it's a drone'. While I never got a good enough look to be certain that the object was a small unmanned device; the FO was in a much better position to visually track the object so I trust his judgment on the matter. In addition; I noted that the object seemed to be very nearly motionless; which would be unusual for balloons; which are generally ascending at low altitudes such as this one. After passing the object; the FO reported the presence of a possible drone just south of our course at present position. The entire event happened so quickly that as the Flying Pilot I didn't take any evasive action; since it appeared that we would miss the object narrowly off our right-hand side. The cause of the event would appear to be someone's reckless decision to intentionally or mistakenly operate a small unmanned device in close proximity to air traffic executing arrival procedures to ORD. Education of small UAV operators is paramount to ensure that folks know that a small unmanned device can pose a significant safety hazard for even such a significantly larger aircraft such as a jet airliner. In addition; I'm certain that the technology exists to detect even small unmanned devices and alert the pilots of larger aircraft to their presence. That technology would be hugely helpful in preventing drone strikes and near misses.




Synopsis: CRJ200 Captain reported a close encounter with a UAV at 4000 feet on the downwind leg for Runway 27R at ORD.
Date: 201810
Local time of day: 1201-1800
Location: ZKC.ARTCC, KS
Flight conditions: VMC
Light: Daylight
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZKC
ATC / advisory: Center ZKC
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We checked in to Kansas City Center at FL280 on an assigned heading. Check in was acknowledged as usual by the controller. Our last ATC clearance was to fly a heading nearly 90 degrees off course; away from our destination; and to expect more in 4 minutes. As nearly 5 minutes had passed; we inquired about our clearance for an update as to when we could expect to turn back on course. A voice sarcastically responded; and reminded us 'we were going to a very busy airport.' As this response was so sarcastic and of no help whatsoever; we assumed it was anyone but an Air Traffic Controller and ignored it; believing the controller and was also ignoring the sarcastic outburst. A short time later; we were given further instructions. The male voice added; 'you can come to the center and apply for jobs.' We complied with the clearance and then realized we had a controller working the sector and another adding (on 2 occasions now) sarcastic; angry comments. It was all very confusing. Upon handoff to Chicago by the controller (professional); we requested the initials of the sarcastic individual who was making everyone's job that much harder; especially the job of the professional controller. We got another rant about how unprofessional we were and an incomplete phone number from the still unidentified voice. We changed frequencies and normal ATC communications resumed. I have never had such a confusing exchange with ATC; never needed to be reminded I was flying into a busy airport; and never have been invited to Center to apply for a job for clarifying a clearance/clearance limit and seeking information for planning purposes. I hope no one has a similar experience.




Synopsis: A319 Captain reported sarcastic unprofessional controller while in Kansas City airspace.
Date: 202010
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 In Charge
Reporter qualification: Flight Attendant Current
Human factors: Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Human Factors

Narrative: We landed approximately 30 minutes early into ZZZ and our gate was not open. The Captain turned off the seatbelt sign and made a PA advising we would be waiting for approximately 25 minutes and the passengers could use the lavatories.After opening the first class lavatory; I phoned the Captain and verified the duration of our hold.  Sometime had passed and from my jumpseat; I utilized an app on my phone and did not realize my actions until several minutes had passed. When I realized what I had done; I was sickened and guilt ridden. Moreover; I was stunned over how automatic and mechanical my actions were without even thinking.In trying to make sense of what I had done; I began questioning myself and realized just how tired I have been from not being able to sleep throughout the recent nights because of stress over current events; specific to our COVID-19 world pandemic; our nation's turmoil; and our carrier's future without the cares act. Nonetheless; with over XX years of experience in performing my duties; I expected more from myself and am extremely embarrassed over my loss of focus; thus the reason for my report. It is my sincere hope that this event may help others.  Please know; I realize my actions were wrong and I take complete and full responsibility. In addition; this event has made me realize the importance of maintaining my focus at all times while performing my duties. To say this was a humbling experience would be an understatement. In closing; again; it is my hope that through this report; it may serve in assisting others in maintaining their focus at all times.




Synopsis: Flight Attendant reported losing focus and using a cell phone app while parked and waiting for a gate.
Date: 202109
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Second aircraft: Small Aircraft
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Workload; Time Pressure; Situational Awareness; Distraction; Communication Breakdown; Confusion
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was approaching ZZZ and handed off to advisory frequency from ZZZ approach. 14 miles from the airport straight in for Runway XX we where monitoring the CTAF frequency prior and heard no one on the frequency we started with our position reports as normal 10 miles 5 miles and 3 miles as we where descending down on the visual approach straight in for Runway XX a Bonanza entered directly on a base 200 ft higher then us I called out their tail number and no response. I decided to initiate a go around as no radio contact was made and don't know what their intentions were.




Synopsis: Twin Engine Pilot reported while on approach to the runway another aircraft turned base to final 200 feet above. The twin pilot executed a go-around to avoid the other aircraft.
Date: 201910
Local time of day: 1201-1800
Location: PHL.Tower, PA
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B PHL
ATC / advisory: Tower PHL
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Ground Incursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: At 300 feet on approach to Runway 27R at PHL a taxiing aircraft was crossing the landing runway at Taxiway F. The flight crew executed a go-around. Flight crew saw the aircraft crossing while on approach below 500 feet. At about 300 feet; flight crew saw that the crossing aircraft was not likely to be clear of the runway in time.The crossing aircraft did not begin to cross the runway until the approaching aircraft was approximately 500 feet final. The crossing aircraft was moving very slowly and at 300 feet final the crossing aircraft was still not close to clear of the runway.ATC should be more vigilant regarding runway crossings while aircraft are approaching. The crossing aircraft did not begin to cross until the approaching aircraft was about 500 feet final and the aircraft was not moving quickly. ATC never notified the flight crew of the crossing traffic.




Synopsis: EMB-145 Captain reported that another aircraft failed to expedite crossing the active runway and caused a go-around.
Date: 201205
Local time of day: 0601-1200
Location: CLT.Airport, NC
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class B CLT
ATC / advisory: TRACON CLT
Reporter organization: Air Carrier
Reporter function: Captain
Human factors: Confusion
Anomaly: ATC Issue All Types; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Procedure
Primary problem: Procedure

Narrative: [We] departed CLT on the JACAL SIX RNAV departure. A CRJ-200 had departed prior to us on the same departure.  Between ZASRO and TASIE; we were instructed to 'maintain 250 KTS'; this given at an altitude of approximately 5;700 FT. Prior to TASIE; was instructed to 'maintain present heading' for spacing. Shortly after passing TASIE; was instructed to 'proceed direct to KATSE; climb and maintain 14;000 FT; rejoin the departure and comply with the restrictions'. After passing thru 10;000 FT; 'After Takeoff Checklist' was preformed and aircraft accelerated to 280 KTS; restriction on the departure. After passing KATSE and climbing through 10;000 FT; Controller asked 'what is your speed'. [ATC] responded with '280 KTS'. Controller response; 'I had assigned you 250 KTS'.  My reply; 'Our last instruction was to proceed direct to KATSE; climb and maintain 14;000 FT; rejoin the departure and comply with the restrictions; 280 KTS is the restriction on the departure'. After a brief silence; we were instructed to turn to a heading of 345 degrees. Moments later a NEW Controller instructed us to 'contact Atlanta Center.




Synopsis: Air Carrier departure from CLT on the Jacal Six RNAV SID was questioned by ATC regarding speed after ATC had vectored the aircraft off and then return it to the SID; issuing 'comply with restrictions'.
Date: 201712
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation - Track / Heading All Types; Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Upon touch down the aircraft veered to the right and ran off the right side of the runway. The aircraft then came back across and ran off the left side of the runway and the nose gear collapsed. There was damage to the nose gear; propeller tip and engine cowling.




Synopsis: PA-28 pilot reported a runway excursion during landing roll out.