elihoole/asrs-aviation-reports huggingface dataset:
Date: 201907
Local time of day: 0601-1200
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Company Policy
Primary problem: Company Policy

Narrative: This aircraft is a retrofitted Airbus 321. [It] has the new bulkhead that does not allow flight attendants to hold the assist handle and if we had to evacuate the aircraft it would prohibit us from doing so which could result in serious injury or death for flight attendants and passengers. This is a huge issue that [Company] and the FAA (Federal Aviation Administration) have known about since day 1; however; they have chosen to not do anything about it. We are told that ready safe go takes precedence over everything. However; that is not true when they are choosing to fly an aircraft that could not be safely evacuated without injury. Fix the aircraft before injury or worst occurs.




Synopsis: A321 Flight Attendant reported new interior is safety deficient.
Date: 201709
Local time of day: 0601-1200
Location: ZZZ.Airport, US
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: Takeoff / Launch
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff; Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: When I added thrust for takeoff; I noticed a strong pull of the aircraft to the right. I had to apply and hold nearly 80-90% left rudder travel to maintain centerline. The wind was variable at 3; and when I checked the trust; the engines were matched. I mentioned the large amount of left rudder to the Captain and he called to continue; suspecting it would correct itself. I brought the thrust up to about 80% at that time then the swerve changed to the left needing about half of the right rudder travel to stay on centerline. The Captain called and accomplished abort; during which we got a brief 'config spoilers' warning message. The Captain immediately checked the spoiler lever and they were already completely retracted and never out of the 0 detent. We exited the runway and contacted maintenance; returning to the gate.I am not sure what cause the aircraft to swerve; but after the abort with the 'config spoilers' message and later on after maintenance had checked the airplane; there was a 'R FLT SPOILERS' caution message that briefly came up on the EICAS.For a moment due to the large rudder required; I stopped moving the levers forward and looked that they were matched about 40% N1. Possibly could have reduced thrust back to idle for a moment to check the directional control of my rudders; then reapplied thrust after; but it's not a real long runway anyway; I think we handled it well by aborting at a lower speed.




Synopsis: CRJ-200 First Officer reported rejecting the takeoff and returning to the gate after experiencing directional control issues early in the takeoff roll.
Date: 202007
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
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 C ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: On approach to Runway XX in ZZZ in VMC; [the] Controller issued [a] visual approach clearance. I began to descend and the aircraft system gave us a terrain caution. We had visual with terrain the whole time and [the] terrain map was pulled up on [the] MFD (Multi-Functional Display). ATC advised terrain clearance and there was no disruption.


Second narrative: During a visual approach into ZZZ; Runway XX during day time conditions; my Captain was [the] Pilot Flying [for] the approach while I was [the] Pilot Monitoring initializing contact with Tower and we got a 'terrain terrain' alert. We did have our terrain up on the MFD (Multi-Function Display). The Captain stopped his descent and climbed until the warning extinguished and was able to continue the approach to a safe landing. We had terrain in sight the whole time and we don't believe my Captain's flying warranted a terrain alert.Terrain alert. Captain flying visual; terrain alert. Stopped descent and climb until alert went away. When flying; just make sure to not descend too rapidly in mountainous areas if this possibly caused the issue.


Synopsis: EMB-145 flight crew reported receiving a terrain warning from the aircraft while in VFR conditions.
Date: 202002
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: Tower ZZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness
Anomaly: Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach; Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Human Factors

Narrative: On approach to ZZZZ Runway X received a GPWS 'Too Low Flaps' alert. Executed successful go around. A combination of factors all taking place in a relatively short time span created a distraction that resulted in omission of necessary procedures allowing proper configuration of aircraft for landing. ATC interruptions for requested position reports along the approach; heavy accent from foreign language requiring repetitive communications increasing workload; steep descent due to terrain separation requiring intercepting the glide path from above and extending the landing gear earlier than normal to increase drag resulting in a disruption of normal flows. Airbus logic for increasing airspeed along the approach to maintain a desired ground speed creating a distraction as a result of strong and gusty winds. It is important to create additional barriers when changes from expectations have taken place; such as extending the landing gear earlier than anticipated so as to prevent potential omission of required tasks.




Synopsis: A320 First Officer reported executing a go-around at ZZZZ airport after receiving a GPWS terrain warning.
Date: 201704
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Light: Daylight
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent; Landing
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Aircraft component: FADEC / TCC
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Distraction; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Maintenance
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; General Maintenance Action; General Release Refused / Aircraft Not Accepted
Contributing factors: MEL; Procedure; Aircraft
Primary problem: Procedure

Narrative: During descent; we had continuous ECAM warnings and cautions associated with the MEL. On short final and after turning the auto thrust off; the number one engine rolled back to idle thrust. We were unable to recover engine thrust on the number one engine. We continued the approach and landed the aircraft without incident. I was very concerned about the aircraft flying the rest of the day with the faults associated with the MEL. I called the safety department hot line representative and the Chief Pilot on duty to voice my concerns determine the proper MEL.

Callback: The reporter believes one of the two Electronic Engine Control Computers was faulty but not properly MELed and possibly still connected. The engine roll back on final with the AUTOTHRUST OFF is a serious event and the aircraft was removed from service.



Synopsis: A319 Captain reported when the autothrust was turned OFF on final; number one engine rolled back to idle. One ENGINE ELECTRONIC CONTROL Computer had been MELed; but he was concerned not properly disconnected. The aircraft was removed from service.
Date: 201909
Location: STL.Airport, MO
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct; Inflight Event / Encounter Bird / Animal
Detector: Person Flight Attendant
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: We were briefed by the operations agent that a customer informed her she would not comply once she got onboard. She was spoken to by the operations agent and a ground Supervisor. However; as soon as we closed the aircraft door; she took her paid pet out and placed the dog on her lap. We called the Captain; opened the door again and she was talked to again by operations agent. She said she would comply going forward; however she was being loud and rude throughout the flight. We need to follow through with what we tell our passengers. She was told that if she didn't comply she would be removed from the flight; she did what she wanted to do and was still allowed to remain on board. If someone blatantly tell us their going to be non-compliant and then prove to do so; they should be penalized.




Synopsis: Flight Attendant reported a passenger refused to comply with instructions to properly stow her pet and became loud and abusive.
Date: 201909
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
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: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Previous crew that brought in aircraft we flew out wrote up some/fumes coming from the cockpit. Maintenance came and deferred pack 1 as they believe that was where the odor was coming from. Upon reaching cruise altitude of FL230; I smelled a strong burning odor; followed by the Flight Attendant and Captain smelling it. The Flight Attendant notified us there was smoke in the cabin. I began a priority handling descent after we put on 02 masks/goggles; and we agreed to divert to ZZZ. We [advised ATC] and landed in ZZZ. After landing and fully stopped on the runway; EICAS message 'PACK 2 OVERHEAT' was displayed. CFR looked over our aircraft; did not detect any hot zones; and followed us into the gate.  Smelled an order by myself; Flight Attendant; and then the Captain; followed by the Flight Attendant stating there was smoke in the cabin coming from rows 11-12. Have maintenance either look over issues more seriously or another aircraft used. We were assured by Maintenance the issue was from pack 1. The Head Maintenance Supervisor mentioned how he had been working since [a long shift] when he signed off on our aircraft. Fatigue may have been an issue.




Synopsis: EMB-145 First Officer reported the entire crew smelled a strong burning odor during cruise resulting in a diversion and uneventful landing.
Date: 202105
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZZ
Second aircraft: Cessna Citation Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Communication Breakdown; Confusion; Workload
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Taxiing out of ZZZZ we called the advisory frequency; we were told there was no inbound traffic and we were cleared to back taxi. It's about a 3;500 foot taxi to the end and roughly 1;000 feet from the end my First Officer points out what seems to be a Citation on a visual left base. We advise the VFR tower that there was an aircraft on final for our runway. Both the tower and ourselves attempted to tell the aircraft to go-around and failed. At this point there is brush and trees lining both sides of the runway and there was no turn off. I pull the aircraft to the right edge of the runway in event that he continued the landing. At an estimated 100 feet; the aircraft was seen adding power and retracting the gear. We advised the tower that we were clear of the conflict and we continued our departure.Suggestions: VFR island flying training or VFR plates to advise of traffic flows to certain airports.




Synopsis: Air Carrier pilot back taxiing at an international non-towered airport reported traffic not in CTAF communications was on approach to the same runway and initiated a go-around on short final.
Date: 201705
Local time of day: 1201-1800
Location: SLC.Airport, UT
Flight conditions: VMC
Light: Daylight
Aircraft: EMB-505 / Phenom 300
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Final Approach
Airspace: Class B SLC
ATC / advisory: Tower SLC
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Distraction; Troubleshooting; Workload
Anomaly: Inflight Event / Encounter Other / Unknown
Detector: Automation Aircraft Other Automation; Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Descending out of cruise onto the STAR into SLC we encountered what turned out to be GPS jamming operations which seriously degraded the Phenom's ability to navigate via RNAV. We advised ATC; requested vectors and ran the AHARs (Altitude and Heading Reference System) 1 & 2 fail checklists. We were vectored for 34R and advised a regional jet was visual for 35 but was unable to make visual contact with that traffic and advised ATC. We were cleared for the visual approach and while on approach had multiple TCAS RAs commanding 'descend' we complied and advised ATC. After the 3rd RA we were below 1200 AGL and requested a break off to the left and was offered a go-around but the TCAS still showed the traffic above us (400 ft). We were able to maneuver for a stable approach and landing after the traffic diverged and we had a 'clear of conflict' call out. I called tower after landing and was told they had no evidence of a conflict and that we were compliant with all ATC instructions.I do not know if the GPS jamming affected the TCAS. This was a difficult situation with traffic depicted above us; responding to the mandatory RA requirements to descend; and the only offer from ATC was a go-around. Obviously things worked out in this instance. I offer this report in the hope that it may create better options for response and to warn other crews of this possibility.




Synopsis: Phenom 300 Captain reported a serious degradation of his ability to navigate due to suspected GPS jamming while descending into SLC. Captain received radar vectors from ATC to the airport; however; they experienced several RAs from an undetermined source during the approach.
Date: 201301
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Eclipse 500
Operator: Corporate
Operating under: Part 91
Flight plan: None
Mission: Ferry / Re-Positioning
Flight phase: Parked
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Training / Qualification; Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Vehicle
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: [I] conducted a maintenance flight to verify a repair. Decided to return aircraft to shop for additional parking brake work. [I] taxied to maintenance door and shutdown engines. Ground crew approached with tug; dismounted; and approached front gear. I was discussing flight with Mechanic who accompanied previous flight when I observed line crewman turn back to tug. I thought he had chocked nose tire the first time and was reaching for tow bar. At this point I prepared to exit aircraft when it rolled forward and struck tug. The collision damaged the radome only. A new radome will arrive and be installed tomorrow morning. Damage report not required as per NTSB 830 reporting instructions but the lesson to be learned is to always act based on established aircraft handling procedures. Had any hand signals been given by the line crewman I would have remained on the brakes and avoided the incident. It was my responsibility to verify the line actions prior to getting out of aircraft. All personnel involved have been briefed and properly trained for future operations. Turnover is a reality at all FBO's; but experienced pilots should not accept handling signal omissions when observed. Properly used standard signals are what ensure safe operations. We have also had a rash of line crew contacting hot pitot tubes while chocking the nose gear at multiple locations across the country. We use special emphasis on preflight now even for a quick turn.




Synopsis: Eclipse 500 pilot assumes that the ground crewman approaching his aircraft is installing chocks and prepares to exit. At this point the aircraft rolled forward and struck the tug.
Date: 201508
Local time of day: 1201-1800
Location: OUN.Airport, OK
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
ATC / advisory: Tower OUN
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Other / Unknown
Anomaly: Ground Excursion Runway; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Weather; Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: During an instructional lesson with my student at the controls we departed the runway surface on our seventh landing. Pilot at controls (student) started veering off left of centerline and instructor attempted to correct with full deflection of the right pedal and couldn't regain control of aircraft. Plane departed into grass; we shutdown the aircraft. No damage to airport property or to aircraft.




Synopsis: SR22 instructor pilot experiences a loss of control by his student on his seventh landing. The instructor takes control but is unable to prevent the aircraft from departing the runway. No damage to aircraft or airport equipment is reported.