elihoole/asrs-aviation-reports huggingface dataset:
Date: 201708
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy
Primary problem: Company Policy

Narrative: Dispatch became aware of multiple North Korean missile launches from an inquiry from a company aircraft.  This desk had one flight headed to South Korea; one flight headed through South Korean airspace; and two flights headed to Japan. The missiles were launched off the east coast of North Korea towards Japan.  Chief Dispatcher researched this incident and advised the Dispatchers that Corporate Security had been advised approximately four hours prior about the missile launch and chose not to advise the Dispatchers.  Dispatch can only speculate on why this information was withheld.




Synopsis: Air Carrier Dispatcher reported that Dispatchers were not advised by their company of missile launches which could have affected the safety of flights operating near the launch area.
Date: 202103
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; Other / Unknown; Physiological - Other; Situational Awareness
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: The Captain refused to brief me along with other crew members because I asked to maintain the appropriate amount of social distance.Captain told me to go to the back if I didn't want to come closer. Not receiving a crew briefing jeopardizes the entire crew along with the passengers.[Suggest] for the Captain when time permits; to brief the crew or brief us individually.




Synopsis: Flight Attendant reported the Captain did not give a crew briefing after the Flight Attendant asked for social distancing.
Date: 202006
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew; Person Ground Personnel; Person Other Person
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On push back from the gate in ZZZ Aircraft X; I was taking with the tug driver reference the previous flight XXXX from ZZZ2 to ZZZ; which I operated; about the live animal in the forward cargo. That is when the tug driver said that's why they put the dry ice in the aft cargo on flight XXXX. I was not informed of the dry [ice] being put in the aft cargo. If the tug driver had not told me that they off loaded dry ice from my previous flight I would not have known.


Second narrative: About an hour after landing at ZZZ after operating from ZZZ2; ramp agent at ZZZ had told us during casual conversation that on the flight inbound to ZZZ there had been 'a bunch of dry ice in the rear cargo compartment'. This was due to a live animal (a laboratory rat) being transported in the FWD cargo compartment. There was no dry ice on the cargo manifest; and I only heard about the dry ice from the Ramper. The load sheet did indicate that there was 250 lbs of cargo in the AFT cargo bay. Upon speaking to the company's HAZMAT Manager; neither he nor company were able to confirm that there was dry ice.


Synopsis: E-175 flight crew reported being notified that their previously completed flight they unknowingly  transported undocumented Dangerous Goods.
Date: 202105
Local time of day: 0601-1200
Location: CPT.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class G CPT
ATC / advisory: CTAF CPT
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine
Human factors: Time Pressure
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: At Cleburne Regional Airport it is hard to see traffic on the other end of field due to center of runway being highest elevation. Traffic was a student who was having trouble with communicating. The plane in pattern in front of traffic had to go around due to the traffic in question joining pattern too close behind them. They announced full stop; however; did not announce taxi back. Prior to taking the runway we announced that we were taking the runway for an east departure and had no response from other traffic. Upon reaching rotation speed we crested the hill and saw traffic; we then rotated and veered to the right side of the runway to avoid over flying traffic. Plenty of separation was maintained. Other flight school instructor was in the pattern as well and they verified they did not hear any intentions of back taxi. The plane in question never made another radio call after short final saying they were landing.




Synopsis: Flight Instructor reported a critical ground conflict during takeoff with a non-reporting aircraft on runway at CPT non-towered airport.
Date: 201211
Local time of day: 0601-1200
Location: ORD.Airport, IL
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ORD
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: We were on Ground Control frequency and instructed to taxi out of the alley to Runway 28ZV via taxiway A to F left on F to M left on M to Runway 28ZV. At the intersection of A and F a refueling truck proceeded to cut in front of our aircraft causing me to stop the plane very quickly. We informed Ground Control of the truck number. After cutting us off; he almost cut off the approaching Express Jet that was taxiing on B. We continued taxiing without further incident. I suggest retraining of ground personnel to emphasize the need to yield to oncoming aircraft.




Synopsis: An Air Carrier made an emergency stop to avoid a fuel truck at the intersections of ORD Taxiways A and F.
Date: 201911
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: 5
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise; Parked
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuel Crossfeed
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Time Pressure; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Weight And Balance; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted
Contributing factors: Aircraft; Chart Or Publication; Human Factors
Primary problem: Human Factors

Narrative: Heavy traffic on way to airport caused Van Driver to drop us off at airport approximately 20 minutes late. We rushed to get to the gate and push as close to on time as possible. I accomplished flight duties while hearing from Captain that we had an MEL 28-X-XX. Right Center Tank fuel boost pump inoperative. I read the dispatch report as did the Captain. After push; and before takeoff; failed to recognize crossfeed valve in closed position (supposed to be open). Took off and at climbout Captain recognized that we had over 1000 pound imbalance from main tanks. We leveled off; referenced the QRH and accomplished applicable checklist. We shut off left center tank boost pump. Balanced mains and turned left center tank boost pump back on. Fuel initially fed from center tank but stopped feeding and started to feed from right main tank causing another slight imbalance. We failed to open up the crossfeed per the MEL which caused this to happen. At the time I was coordinating and programming for a diversion. Landed in ZZZ as a divert. Captain recognized the error after talking to Maintenance via telephone call.




Synopsis: B737-700 First Officer reported that distraction and time pressure caused the crew to miss a checklist item that resulted in a fuel imbalance and a diversion.
Date: 201204
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain
Light: Dawn
Aircraft: Airbus 318/319/320/321 Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Human factors: Time Pressure; Situational Awareness; Training / Qualification
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Other Takeoff Roll
Result: Flight Crew Returned To Gate; Flight Crew Rejected Takeoff
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On takeoff roll; below 80 KTS; [we received an] ECAM 'ENG 2 COMPRESSOR VANE'. Captain assumed control of the aircraft and aborted. Autobrakes engaged and we could hear sounds of compressor stall. We advised flight attendants to remain seated. As we exited the runway; ECAM 'ENG 2 FAIL'. EGT was RED and we accomplished all ECAM steps; including suspected damage. We checked the brake temperatures; and with no other adverse indications; we taxied to the gate. We had ground crew chock the aircraft and released the brakes to cool them.


Second narrative: [Narrative #2 contained no additional information]


Synopsis: An A320 series ECAM alerted 'ENG 2 COMPRESSOR VANE' below 80 KTS on takeoff; then after the reject the ECAM alerted ECAM 'ENG 2 FAIL' and also 'EGT HIGH'. The aircraft was returned to the gate.
Date: 202008
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Company Policy; Human Factors
Primary problem: Company Policy

Narrative: Came to work the following day after being tested the previous day for COVID-19. Was notified a close co-worker tested positive for COVID-19; who I was in contact with the day of my testing to help him make an appointment for his test. I wasn't notified by management regarding his positive testing and continued to work.




Synopsis: Ramp worker reported that a co-worker tested positive for COVID-19. The ramp worker was not notified by management and continued to work.
Date: 202103
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Weather / Turbulence; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Contributing factors: Weather
Primary problem: Weather

Narrative: I was flying solo in an experimental aircraft and just as I was touching the ground on landing experience a wind gust from the right side. I ran out of right rudder and the plane tipped onto the the left wing tip starting a ground loop at approximately 15 mph ground speed. The tail spun around; a prop-strike occurred; then a tail-strike. I climbed out of the aircraft after shutting everything off and was uninjured. The airplane sustained some damage to the empennage and a propeller. No property damage or harm to any person occurred.




Synopsis: Pilot of an experimental aircraft reported a wind gust spun the aircraft out of control causing a prop and tail strike.
Date: 201905
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON ZZZ
Aircraft component: Rudder
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Procedure; Company Policy
Primary problem: Aircraft

Narrative: While on approach with the flaps extended and autopilot engaged; both pilots felt the rudder pedals rapidly moving about an inch or two. The rudder pedal movement stopped when the autopilot was disengaged and did not reoccur. After entering the incident in the log book; I was contacted by a member of my union's safety committee who informed me that there have been approximately a dozen similar instances on this particular aircraft.




Synopsis: A321 Captain experienced rudder vibration in flight.
Date: 201505
Local time of day: 0601-1200
Location: CHD.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Mission: Training
Flight phase: Initial Approach
Airspace: Class D CHD
ATC / advisory: Tower CHD
Reporter organization: Personal
Reporter function: Instructor
Human factors: Situational Awareness; Distraction; Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: While starting to turn to enter left downwind for runway 22L at CHD (from the south) a near miss occurred as another aircraft was turning from crosswind to downwind. Neither traffic was issued any kind of advisory or instruction regarding the other one. As I saw the aircraft and pointed to it my student turned right to a wider downwind to avoid the other aircraft. The pilot of the other aircraft asked if ATC was aware of us and ATC replied yes and quipped that we hadn't reported downwind as instructed; even though we hadn't entered downwind when the near miss occurred. The other aircraft was instructed then to follow us and the rest of the pattern was uneventful. On upwind the tower reprimanded us for not reporting downwind and responded that we [were] unable due the conversation ATC was having with the other aircraft.CHD tower controller did not issue any advisories for the traffic nor did they instruct either aircraft of which one should be number. The other aircraft had departed runway 22L for left closed traffic while we were on a downwind entry. An advisory to us about the traffic on upwind would have helped a lot or if ATC had instructed the other aircraft to plan to follow us.




Synopsis: An instructor pilot approaching the CHD Runway 22L landing pattern in a crosswind to downwind entry had a near miss with an aircraft in the landing pattern after ATC failed to notify either aircraft of the others presence or issue controlling guidance.
Date: 201505
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: TCAS Equipment
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Distraction
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On descent we were passing through FL210 when we got a TCAS RA. The TCAS showed a target at our precise location and at our exact altitude. The Captain responded to the RA and descended. When we got to about FL203 we got another TCAS RA that told us to climb. The TCAS showed a target again at our exact location and altitude. The Captain again responded to the RA. The RA and target disappeared after a climb of about 100-200 feet. We reported all of this to the Center Controller who said that he showed no aircraft in our vicinity. He said he would write it up on his end but that he recommended we check our equipment. It appeared to us that our TCAS was responding to our own aircraft as an intruder aircraft. The Captain said that he had heard of this happening during the early days of TCAS use. After landing the Captain wrote up the TCAS and called Maintenance to explain the writeup.


Second narrative: During descent on the STAR descending through FL210 we got a TCAS RA red symbol on nose of our aircraft ND symbol and 'descend' aural command. I disconnected autopilot and increased rated outside of red bar. Subsequently we got a pitch reversal TCAS RA to 'Climb' aural message at FL202; which I smoothly complied with. We informed ATC; he said no traffic in our area. He said 'May want to get our equipment checked.' We saw no traffic visually. Upon block in; we wrote up the TCAS and verbally informed Maintenance.


Synopsis: During descent a B777 TCAS generated an apparent false traffic target and issued a descend command followed by a climb command. ATC reported no traffic in the area so this is an assumed null bus fault.
Date: 201911
Local time of day: 1201-1800
Location: PHL.Airport, PA
Flight conditions: IMC
Light: Dusk
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B PHL
ATC / advisory: TRACON PHL
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Human-Machine Interface; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Human Factors; Company Policy
Primary problem: Aircraft

Narrative: Upon arrival after setup and verification of the GPS we were on vectors for the approach. After being cleared for the approach and reaching the final approach fix; my GPS lost both the FPA and lateral guidance. I called out the loss of GPS guidance and the Captain called for a go-around even though his GPS continued to operate properly. We executed the missed approach; set the approach back up; ran our checklist and transferred controls. We also noted the presence of the FMS message SBAS 2 NOT NAV on the right side FMS. The Captain flew the next GPS Approach and landed the aircraft with no further incident.




Synopsis: EMB-145 First Officer reported the Captain called for a go-around after the First Officer lost GPS guidance signal.
Date: 201711
Location: IAH.Airport, TX
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Situational Awareness
Anomaly: Other Jet Blast
Detector: Person Other Person
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport
Primary problem: Airport

Narrative: All aircraft are 737's. Aircraft X was told to push [to spot on ramp]. Aircraft Y was told to push to R right behind Aircraft X. The agent on the push crew for Aircraft Y had to get jet blast from Aircraft X. Right after that while those planes were still in there spots flight Aircraft Z was instructed to push to [a different spot]. Next while the first 2 flights are still at their spots Aircraft Z was instructed to push out of the gate to spot Q. Aircraft Z had to push through Aircraft Y's jet blast to make it to spot Q where the crew then got jet blasted from Aircraft A as it started to taxi away.




Synopsis: Ground reporter stated that simultaneous push-backs from a terminal in IAH is a safety hazard due to jet blast from airplanes in front of one another.