elihoole/asrs-aviation-reports huggingface dataset:
Date: 202006
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Flight phase: Parked
Reporter organization: Fractional
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Confusion; Workload
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Other Person
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Environment - Non Weather Related; Company Policy; Procedure
Primary problem: Procedure

Narrative: It was brought to my attention that; a digital message in reference to adding a work order for LED light installation was not applied. I do not remember my work load for the day; but I do know it was my second day on duty by myself with over 150 flights. Unless someone else had opened the digital message I can only assume it was me that read the message and did not apply the work order.Suggest that the desk be staffed in a manner that we can safely do our work; even in the financial times the company is in now. During the lack of manpower I need to tell myself to not to take on more of a workload than I can handle.




Synopsis: Technician reported a work order was missed and not completed.
Date: 201702
Local time of day: 1801-2400
Location: LAX.Airport, CA
Light: Night
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Workload
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
When detected: Pre-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I filed [the] flight LAX/ZZZ on Route 22 [so] as to not use the LOOP9 departure due to the later departure time. Route 22 was compliant with the existing; at the time; ZZZ Wind Route. ATC issued a reroute over TRM-PKE-DRK-J134. I built the re-route; but I could not profile the altitude down low enough to get below the turbulence which was from FL270-350. The ATC re-route when through blocked airspace between PKE and DRK below FL280. I needed to file at FL250 to avoid getting turbulence indicators of '3' on my flight plan. I had to call ZLA and then I had to call our ATC desk who had to call the Command Center to get approval to file the original route at FL250. This all took a lot of time to coordinate between all parties involved. ATC did not take into account the turbulence in the LAX area when issuing the reroute.ATC needs to taking into consideration turbulence and thunderstorms when issue mandatory re-routes so it does not become a safety of flight issue.




Synopsis: Air carrier Dispatcher reported it took a long time to get the needed planned altitude from ATC to avoid an area of turbulence.
Date: 201407
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 8
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Other / Unknown
Anomaly: Ground Excursion Runway; Inflight Event / Encounter Loss Of Aircraft Control
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Regained Aircraft Control; Flight Crew Rejected Takeoff
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon landing; the aircraft bounced. I attempted to salvage the landing with the appropriate attitude and a very little bit of power to soften the next landing attempt. The plane bounced again. This got me nervous; I remembered I shouldn't try to save a balked landing. (And this is why) On my attempt to go-around; I applied full power (I do not remember if I turned off the carb heat) I did not raise my flaps at all. Left turning tendencies were in full effect as I tried to fly out and go-around. As soon as I flew out of ground effect; the plane dropped (as it should) onto the grass between the runway and Taxiway Alpha. I successfully and safely brought the aircraft to a safe stop on the grass and then proceeded to an intersection towards Taxiway Alpha. I brought the aircraft to a complete stop immediately after the hold short line and requested to bring the aircraft back to the south ramp in order to park the plane. They approved my request. I asked if any report had to be made. The Controller did ask me to call the Tower after; which I did.




Synopsis: During landing this 150 hour Cessna 172 student pilot bounced; applied bounce recovery techniques; bounced again; decided to takeoff; and after an unsuccessful go-around attempt came to a stop in the grass off the runway.
Date: 202104
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class D ZZZ
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Observer
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Procedure

Narrative: I was watching from the ground near the hangars on the north side of Runway XX.  My student had completed two successful patterns to a full stop.  On his third final approach; he appeared to be on a normal descent until approximately 100-50 feet AGL.  The aircraft then appeared to increase descent towards the runway.  He pulled the aircraft to level flight just before the aircraft touched down.  The aircraft touched and bounced back into the air.  My student lowered the nose as the aircraft started to descend.  The aircraft began to porpoise.  On the third porpoise; the aircraft departed Runway XX on the left hand side; the nose gear collapsed and the aircraft came to a stop just off the runway.I need to re-enforce with this student what to do when the aircraft bounces.  A pitch attitude above the horizon must be maintained throughout the bounce and a go-around must be initiated.




Synopsis: Flight instructor reported observing his student during first solo flight lose control of the aircraft during landing resulting a landing gear collapse.
Date: 202011
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Initial Climb
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Human-Machine Interface
Anomaly: Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Software and Automation
Primary problem: Human Factors

Narrative: It was the Captain's leg on a return flight from ZZZ when we were given the ZZZZZ3 SID. We were given a standard take off clearance from Runway XXL (no heading; altitude; or fix to fly) and I; as the pilot monitoring; engaged the autopilot modes as directed. When I engaged the NAV mode; it did not arm FMS but instead HDG mode. After double-checking I correctly engaged NAV mode; we were still in HDG with the only white needle navigation being from ZZZZZ to ZZZZZ1 and then on the rest of the departure. Since we were still in HDG mode with what I remember was runway heading bugged; we were heading directly for the terrain off of the departure end of XXL. We received hasty instructions from ATC to turn left immediately to get away from the terrain; which we complied with. We were in VMC and could clearly see the terrain; which we had already climbed above when the instructions from ATC came through to start the immediate turn. We never received a GPWS terrain alert. Once established heading back to ZZZZZ on the departure; the Captain had disengaged and reengaged the NAV button to finally arm FMS mode. ATC then advised us to resume the departure and continue our assigned climb altitude to 17;000 feet. No further communications between us and ATC about what had happened. The rest of the flight went on normally and without incident. Really make sure on RNAV departures that when you select the NAV button that the FMS mode activates and if needed spin the heading bug to the headings provided on the charts to avoid conflicts like this.




Synopsis: Air Carrier First Officer flying CRJ-900 aircraft reported flying toward terrain on departure.
Date: 201603
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Vehicle Driver
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: After moving Aircraft from hangar spot to the gate; I was pulling away from aircraft; stopped to let my partner in tug; and then proceeded to leave gate. Had to stop because steering in the tug locked up; could not turn steering wheel. This tug is a Hybrid with drive by wire technology. I was able to regain steering by turning off tug and recycling the computer. The problem came up again some 50 feet later when I stopped again. Had this happened while towing an aircraft there would have been major damage to an aircraft as well as injury to employees.




Synopsis: Tug Driver reported their drive-by-wire tug lost all steering due to a malfunctioning computer.
Date: 201908
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZZ
Reporter organization: Air Carrier
Reporter function: Check Pilot; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Workload; Situational Awareness
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On taxi out to RWY XXL from north end of airport taxiing east bound on Bravo was advised to turn right onto Lima south bound. Was told to give way to traffic nearing Bravo. Was looking for traffic and conducting minor cockpit workload when we passed Lima taxi way just enough to not be able to make the turn. Advised ground that we were on Bravo not Lima if they could work with that. They advised no issue to continue on Bravo.  My fault that I missed the taxiway. Signage to me was slightly confusing but not enough to have made an appropriate turn onto Lima taxiway.  We are aware of the confusion that this intersection can cause for us but I made the mistake with the clearance I was given.


Second narrative: After pushback from Gate X at ZZZZ we were given taxi instructions to taxi Hotel turn right on Bravo then Lima short of Lima2. We inadvertently missed Lima and continued on Bravo and notified ground control that we missed Lima taxiway. They said no problem and gave us new taxi instructions to Runway XXL. We continued to taxi to Runway XXL via the new instructions without incident. We may have missed taxiway Lima because it can be confused with a ramp entrance.


Synopsis: Flight Crew flying 777-200 encountered taxiway incursion during taxi for takeoff.
Date: 202008
Local time of day: 1201-1800
Location: ACT.Tower, TX
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Flight plan: VFR
Flight phase: Other VFR Traffic Pattern
Airspace: Class D ACT
ATC / advisory: Tower ACT
Reporter organization: Government
Reporter function: Flight Data / Clearance Delivery; Supervisor / CIC; Local; Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Physiological - Other
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
When detected: Other During shift
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Working the tower CAB combined; I was filling the role of clearance delivery; local control; ground control; and tower CIC (Controller in Charge). There was an average amount of traffic for the time of day; and it was picking up. As it got busier I was moving around the tower cab more. This movement caused a yellow jacket wasp; maybe two; to stir and start flying around the tower. As I do not know if I am allergic to wasps or not; this was very concerning. This also created a very distracted work environment and a possibly unsafe situation for the aircraft that I was controlling. This is a reoccurring event and management has been notified. The city manager left a spray can of insect killer as the 'remedy' for the situation. This is not a solution at all; but it was what was available since they were flying over my head and dive bombing me. I had to spray the wasp as it landed on the window. This also created an issue as the spray ran down the window and partially obstructed the view out of said window. There is a current UCR (Unsafe Condition Report) on file for this same issue; as it has happened a lot in the past. Fix the holes in the tower cab allowing the wasps and other insects to enter from the outside.




Synopsis: Tower Controller reported wasps flying around the Tower Cab create an unsafe distraction.
Date: 201907
Local time of day: 0601-1200
Location: RIC.Airport, VA
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Corporate
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Received verbal clearance on ground. Richmond read fixes and did not spell. Route was completely different than filed. I thought GREKO was a fix I was issued and read it back. As a crew we dual verified clearance and distance was close to what it should be. Enroute ATC cleared us direct GREKO. Shortly thereafter; Controller asked us where we were going. We told Controller GREKO. I told my partner to spell the fix for Controller and he did. Controller informed us it was GRACO; not GREKO and gave us a heading. There were no traffic or airspace conflicts that I was aware of.




Synopsis: Citation 560XL pilot reported fix they thought was GREKO; but was actually GRACO; causing confusion.
Date: 201506
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant; Person Passenger
When detected: In-flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On our flight I saw a passenger was crying while I was is the middle of doing our demo. After we finished our demo I asked her what was wrong and she stated that she had some anxiety about flying and had a rough flight on last flight from (city). I offered her a ginger ale beverage and she accepted and I told the young lady if there is anything that I can do to make her flight more comfortable to don't hesitate to let me or the A Flight Attendant know. I then went to advise the A Flight Attendant of the situation on how the young lady was feeling some anxiety and that she was a little shaken up. The A Flight Attendant then asked her age.  The young lady told her that she was only 20 years of age. Then the A Flight Attendant; insisting and I Quote 'Your close enough!! Don't worry I'll Take Care of You!!!;' told a 20 year old that she would make her an alcoholic beverage after the young lady told her she was ONLY 20 years old.  The young lady's Clinical Counselor that was traveling with her was very appalled and thought the comments that the A Flight Attendant made to offer her an alcoholic beverage was very inappropriate. The Clinical Counselor did advise me that she will be writing about the whole encounter. I then apologized on behalf of myself; the A Flight Attendant and the entire company for the statements that she made to the young lady.I did advise the Captain about the whole situation.The A Flight Attendant should have never offered a beverage to an under 21 year old passenger especially when she advised her that she was under 21 years old.  She could have simply stated to her that if there was anything that I could do to make your flight more comfortable please let her know.




Synopsis: EMB-175 Flight Attendant notices a young lady crying during the safety demonstration and inquires as to the cause. She is informed that the lady is a fearful flyer and the A Flight Attendant is informed. The A Flight Attendant; after learning that the young lady is 20 years old; offers an alcoholic beverage in violation of company rules.
Date: 201211
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Aircraft: No Aircraft
Reporter organization: Government
Reporter function: Approach; Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Other / Unknown
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: ARTS ll Limited RADAR limited in today's aviation standards. I was a CPC at a large facility for many years. I transferred to a lower facility for family reasons. The RADAR display at this lower level facility is a disgrace to the FAA; air traffic controllers; and the flying public. The display is unreadable; the sweep is outdated and the equipment is from the 1960's. With the preference on aviation safety and NEXTGEN; this facility needs to be RADAR updated. This is unacceptable. Cell phones have a better display and capabilities than this RADAR. What event will it take to update this equipment and at whose expense; the flying public; air traffic controllers; or the FAA when a disaster happens because of the outdated equipment. Coming here is like coming back to the dark ages; the twilight zone; prehistoric ages.




Synopsis: TRACON Controller using ARTS 11 Limited RADAR voiced concern regarding the outdated equipment; indicating this subject equipment is unsafe.
Date: 201910
Local time of day: 1201-1800
Location: PIT.Airport, PA
Flight conditions: VMC
Light: Daylight
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Other remote pilot
Operating under: Other 107
Flight plan: None
Mission: Other structural inspection
Flight phase: Cruise
Airspace: Class B PIT
ATC / advisory: TRACON PIT
Reporter organization: Contracted Service
Reporter function: Other / Unknown
Reporter qualification: Other Remote Pilot
Human factors: Confusion; Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Other Person
When detected: Routine Inspection
Contributing factors: Airport; Airspace Structure; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: I looked up the address on FAA/UAS S Chart. I misinterpreted the LAANC grid. I thought below 400 feet was Class G airspace. This was discovered by the company that does monthly reviews. The manager of this program brought the violation to my attention. We got together and discussed misunderstanding of the airspace and will get the authorization in the future.




Synopsis: A Drone pilot reported a Class B airspace violation.
Date: 201209
Local time of day: 1201-1800
Location: SEA.Airport, WA
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B SEA
ATC / advisory: Tower SEA
Aircraft component: Radio Altimeter
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; General Maintenance Action
Contributing factors: Human Factors; Procedure; Aircraft
Primary problem: Aircraft

Narrative: With clear weather at SEA we decided to do a practice auto-land. We briefed; setup; and advised both Approach and Tower of our intention. Just after my 150 foot call the autopilot and autothrottle disengaged. I took control manually. The landing resulted in a bounce with a subsequent touchdown. I entered the unsuccessful auto-land in the maintenance logbook. The landing was not good from a pilot's perspective but was not hard by Maintenance definition. There was no aircraft generated advisory message or visible indications of a hard landing. The Maintenance Technician confirmed that oil marks on the landing gear struts only indicated partial compression. Other than some light hearted remarks there were no complaints of injury by passengers or crew. This event has completely changed my opinion of our current auto-land procedure and the need for our pending change. The maintenance BITE revealed that the automation disconnected because the Captain's Radar Altimeter failed at 75 FT. I had not yet said that I had the aircraft but it was so close to that point that the First Officer thought that I did. Thankfully and to his credit he verbalized that I was now the pilot flying. Fifty feet is not the place for a transfer of control especially when it is from automation to First Officer to Captain.




Synopsis: Air Carrier Captain experiences autopilot disengagement at 75 FT during an auto land approach in VMC. A firm manual landing ensues after a small bounce. Maintenance determines that the Captain's radar altimeter failed at 75 FT causing the autopilot disengagement.