elihoole/asrs-aviation-reports huggingface dataset:
Date: 202006
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: M-20 Series Undifferentiated or Other Model
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Confusion; Situational Awareness
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: Airspace Structure; Human Factors; Airport; Procedure
Primary problem: Human Factors

Narrative: Two pilot training mission was launched out of ZZZ1-ZZZ2 in Aircraft X then Direct to ZZZ.  The winds at ZZZ 010 @ 7 kts.  We decided to land runway XX and enter right traffic as published.  On approach; we did not see any other aircraft on TCAS.  We made radio calls starting at 5NM West; to join midfield downwind after crossing midfield.  We made additional radio calls with no response on the overhead; downwind; base; and final for runway XX.  Upon turning final; we noticed nothing abnormal and continued the final decent.  We entered the flare and during the flare; saw a landing light approaching on the centerline opposite direction on Runway YY.  We immediately began a go-around and offset to the east of the centerline and climbed out to rejoin the pattern missing the other aircraft by roughly 100 feet. Aircraft Y; that was on the runway did not make any known radio calls or take evasive action.Additionally; at no point did we get a TCAS warning from our system.After landing; we made contact with the other pilot who explained he had the frequency input incorrectly into his radio and claimed to have been making calls without response.Aircraft Y's lack of calls and long straight in approach over the lake instead of flying the pattern made them hard for us to spot.




Synopsis: A SR22 Instructor Pilot reported a NMAC with opposite direction landing traffic at a non-towered airport.
Date: 202103
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: Wind
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Flight Dynamics
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Human-Machine Interface
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Landed As Precaution; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On departure lost Number 2 Pitch Trim; Autothrottle; 1 and 2 Autopilots and FO (First Officer) Flight Director. Number 1 Pitch Trim already deferred. Also; MEL that restricted us from RVSM airspace. Performed ECAM/ QRH procedures and could not reset Pitch Trim or Autothrottles. No autopilots were recovered and only manual trim available. [Received priority from ATC] as a precautionary measure. Returned to departure airport ZZZ. No further problems noted. Uneventful landing.Cause - System malfunction of Pitch Trim and Autopilots.Suggestion - Will await Maintenance final action/correction.


Second narrative: On departure at acceleration altitude we had Pitch Trim 2 fault. Pitch Trim 1 was already deferred. The ATS (Autothrottle System) lever also tripped off and I had FD2 flag on my pad. After the aircraft was cleaned up and the after takeoff checklist completed. I selected my FD switch to get FD1 on my PFD (Primary Flight Display). We accomplished the ECAM. Neither Pitch Trim 2 or ATS off reset. We ran the pitch fault QRH. It was no help. We elected to [advise ATC] and land in ZZZ.Cause - Pitch Trim 2 fault with Pitch Trim 1 deferred already.


Synopsis: Air Carrier flight crew reported loss of Pitch Trim and Autopilots after takeoff resulting a return to departure airport.
Date: 202110
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: Gulfstream Jet Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Communication Breakdown; Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: While taxiing from the southeast ramp; westbound on taxiway 1; Ground Control issued us the following clearance; 'Aircraft X; taxi to Runway XXL via [Taxiway] 2; cleared to cross Runway XY; give way to Aircraft Y on [Taxiway] 3.'  As we turned southbound onto Taxiway 2; as I was looking right to clear for crossing the runway; the Captain brought the aircraft to an abrupt stop and I noted a 767 taxiing westbound on Runway XY.  Luckily the Captain saw them before we hit them.   We queried Ground Control about the conflict and we noted that the 767 crew remarked; 'That was a close call'.  There was never any mention of giving way to a 767 taxiing westbound on Runway XY in our taxi instructions. Human Factors breakdown.


Second narrative: While taxiing to Spot X on Taxiway 1; Ground issued the following clearance just prior to reaching Spot X:  'Aircraft X Taxi to Runway XXL via [Taxiway] 2; cleared to cross Runway XY; give way to Aircraft Y on [Taxiway] 3.' As I turned the airplane onto Taxiway 2 (north side of Runway XY) to cross Runway XY; I had to yield/stop uninstructed to give way to a 767 aircraft taxiing on Runway XY westbound from my left to avoid a taxi incursion with that aircraft.


Synopsis: Pilots reported a ground conflict with an unknown aircraft while looking for ATC issued traffic.
Date: 201706
Local time of day: 0601-1200
Location: CLT.Airport, NC
Flight conditions: VMC
Light: Daylight
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 CLT
ATC / advisory: TRACON CLT
Second aircraft: A321
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: ATC Issue All Types; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Regained Aircraft Control
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: Encountered wake turbulence on visual approach to 23 in CLT. We were cleared down to 4000 ft. to intercept the glide slope at ATELL. We were about 1 dot below GS at assigned altitude of 4000 ft. when the airplane hit wake and rolled right past a 45 degree angle (estimated). My FO was flying; but I immediately clicked off the autopilot and rolled the aircraft level. It took a couple seconds as the aircraft reacted very slowly even with near full deflection back to the left. We advised ATC and continued the approach just above GS.[Caused by] wake from an A321 3 miles ahead of us.[Recommend] better descent clearances to avoid descending wake from interfering with aircraft intercepting GS at lower altitude.




Synopsis: ERJ-145 Captain reported encountering wake turbulence that resulted in a 45 degree roll on approach to CLT 3 miles in trail of an A321.
Date: 201902
Flight conditions: VMC
Weather elements / visibility: Turbulence
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
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: Communication Breakdown; Time Pressure
Anomaly: ATC Issue All Types; Deviation - Speed All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Airspace Structure; Procedure; Weather
Primary problem: Weather

Narrative: Westbound on NAT D (North Atlantic Track D) at assigned FL390 and assigned mach .82; we experienced moderate turbulence. We slowed from mach .82 to mach .80 to improve the ride. We notified Gander via CPDLC(Controller Pilot Datalink Communications) of the change immediately; and received an acknowledgment shortly after via CPDLC. [A few minutes later]; the ride improved. We accelerated back to assigned mach .82; notified Gander via CPDLC immediately and again received acknowledgment via CPDLC. Shortly after; we received a message via CPDLC; something to the effect of Next time; make request prior to change. No further communication related to this scenario. Flight continued uneventfully to full stop landing.Change in speed was effected to improve the ride in moderate turbulence. If ride and timing permits; notification to ATC should be made in advance of speed change.




Synopsis: A330 First Officer reported moderate turbulence resulted in a speed reduction before making the request with ATC.
Date: 202006
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Procedure; Human Factors; Environment - Non Weather Related
Primary problem: Company Policy

Narrative: Arrived at ZZZ flight operations to find COVID-19 protocols being used and social distancing being encouraged. The same protocols are in place for boarding and riding the crew buses to our aircraft. We are also encouraged to wear masks in the presence of ramp and maintenance personnel when they board the aircraft. We even found a note saying the cockpit had been sanitized at some point. So; the COVID-19 safety protocol chain was intact until we reached the cockpit. What we did not find however; were any alcohol-based wipes with which to clean our headsets or wipe down knobs; levers; seatbelts and other touch points in the cockpit. I know the cockpit was supposedly sanitized; but I am not sure that every touch point; especially the headset microphones; would be adequately cleaned by the cleaning crew. The only wipes on board the aircraft were Sanicoms and M-Zone Screen Wipes. Both of these wipes have been shown to be ineffective against the COVID-19 virus. My question and concern is why weren't there any Purell Hand Sanitizing Alcohol wipes; or something comparable on board our aircraft? When I called the Flight Safety Department to inquire about this issue; I was encourage to go ahead and submit a report to highlight this safety shortcoming.Inadequate sanitary supplies effective against the COVID-19 virus on board the aircraft to wipe the touch point surfaces on the aircraft.Replace the ineffective Sanicom wipes that are part of the cleaning crew's supplies with an adequate supply of Purell or other alcohol-based wipes that are effective against COVID-19.




Synopsis: Air carrier Captain reported having inadequate cleaning supplies to sanitize their cockpit equipment.
Date: 201710
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dawn
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Had a RTO (Rejected Takeoff) at 50 kts; got an aural warning for flap mis-configuration; exited the runway; ran checklist; flaps were set to 1; reset to position 8; called MX (maintenance); waited 15 mins and continued with the flight.Flaps were at position 1 not 8.




Synopsis: CRJ900 First Officer reported a rejected takeoff due to incorrect flap setting.
Date: 201310
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: Marginal
Weather elements / visibility: Rain; 10
Light: Night
Aircraft: Beech 1900
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Instrument and Control Panels
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: On descent the First Officer noticed that the First Officer's Display Select Panel on the center console was installed upside-down. All aspects of the panel worked correctly but due to the upside-down installation; the button to set the decision height was on the top of the panel not the bottom. After discussing this with the Captain; we determined that we would get a visual that night and we felt it was not a safety of flight issue. We continued to ZZZ which was about 15-20 miles away at this time and broke out about 4;500 FT AGL and landed without incident. Once on the ground we called the company's Maintenance Control and wrote it up and they had a Mechanic come out and fix it. The flight to ZZZ is about 30 minutes and involves two VOR's and a heading of 258. Even though it was a visual approach company policy states we have to setup an approach at night. Due to the short flight and marginal use of the panel it was not noticed until setting decision height and finding the knob not in the usual place. Although it was not in the usual place it was fully functional and the approach was set up without any issue. Some reasons why it was not noticed earlier was due to a dark ramp; very little lighting upon the center console of the aircraft; the panel looking almost identical either way it is installed (only three small buttons on top not bottom); the First Officer boarding passengers while the Captain was setting up the flight deck; and lack of use on this flight as it was a short flight on a 258 heading with a straight in approach. Due to the short flight; visual approach; and ZZZ being our destination and closest airport at the time the issue was discovered we determined it was not a safety of flight issue and proceeded with a normal landing and had it fixed by a mechanic prior to the next flight.




Synopsis: BE1900 First Officer discovers his Display Select Panel on the center console was installed upside-down during approach set up. The panel was fully functional and corrected by Maintenance after landing.
Date: 201602
Local time of day: 0601-1200
Location: BUR.Airport, CA
Flight conditions: VMC
Aircraft: Citation Excel (C560XL)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Engine Air Starter
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Aircraft; Manuals; Human Factors
Primary problem: Manuals

Narrative: While starting the right engine; the GPU went offline aborting the start. I followed the QRC for abnormal start and secured the engine. I had the ground crew remove the GPU and started the left engine on battery power. After limitation wait time; I started the right engine using generator assist. The right engine started; but the starter would not disengage. I again followed the abnormal start QRC; but while the engine shut down; the starter would not disengage. I used the right engine fire switch to secure the engine.The Encore+ QRC does not have; nor points to the more expanded abnormal start procedure that exists in the QRH. That procedure would have most likely resolved the stuck starter without having to use the engine fire switch. I did not think of this procedure as I was concerned about major damage or even an engine fire with passengers on-board. I suggest that the full engine start malfunction procedure be incorporated in the QRC; or at the very least; the QRC point to the appropriate section in the QRH should the QRC actions not resolve the abnormal start.




Synopsis: CE-560EP Captain reported the right engine starter failed to disengage and the procedure to resolve the issue was not in the QRC.
Date: 202008
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Post flight
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Other Posst flight completion
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Stores Dangerous Goods shipment - (UN1219; Class 3; flammable; Isopropanol; 3.8 Liters X 4 Pieces); four total pieces at 44lbs gross weight; was sent from ZZZ to ZZZ1 and should have terminated in ZZZ1. ZZZ2 reported that they received one of the four pieces without paperwork; proper manifesting on that flight; and notice to the Captain was not sent to the flight deck. The aircraft for both flights was the same aircraft with tail number.




Synopsis: Airline ground personnel reported undocumented Hazmat transported to subsequent downline station due to not being off loaded at first station.
Date: 201409
Location: PHX.Airport, AZ
Flight conditions: VMC
Weather elements / visibility: 20
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Flight plan: VFR
Mission: Personal
Flight phase: Climb
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy

Narrative: Forgot to turn on transponder while within the 30 mile radius around Phoenix. Turned on transponder when I noticed it was off.




Synopsis: A small aircraft pilot forgot to turn on their transponder while flying within a 30 mile radius of PHX Class B airspace.
Date: 202011
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: Physiological - Other; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Pre-flight
Contributing factors: Human Factors; Company Policy; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: The aircraft was late arriving. There were fumes and a very strong smell coming out of door 1L from the sanitizing spray while we were standing out on the jetway. The training that all FAs are required to complete; states we must wait at least XX minutes before entering the aircraft after spraying is completed. The agents started boarding while we were still on jetway and the customers told the agents. So the gate agents came down to ask what the problem was and we stated the fumes are too strong for us to board. We were pressured to start boarding as to not cause a delay!




Synopsis: Flight Attendant reported the gate agents tried to board the passengers right after the aircraft was sanitized; disregarding the mandatory wait time.
Date: 201705
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: SA-227 AC Metro III
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Main Gear
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On a visual approach I had my first officer put the gear down; and called for the before landing checklist. We got 2 green and 1 red light on the gear indicator. The left main was not down; and also felt that the aircraft began to yaw because of it. We cycled the gear 3 times; and got the same indication each time. We then performed the emergency gear extension checklist; but still had the same gear indication. At this point we were about a 4 mile final; and told Tower we are having a gear issue and would like to circle somewhere to see if we can get it down. Right after saying that the left main gear popped down. We continued to land without any other incident.




Synopsis: SA-227AC Captain reported the left main gear finally extended after multiple extension attempts.