elihoole/asrs-aviation-reports huggingface dataset:
Date: 202112
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Cargo Compartment Fire/Overheat Warning
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action; General Evacuated; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The pilot in command and I were taxing down Taxiway XX for a Runway XX departure from ZZZ. During the taxi; the red Baggage Smoke" annunciator turned on. The pilot in command decided to shut down the aircraft and evacuate the aircraft on the taxiway. We informed Ground Control of our intentions; and while the pilot in command completed the emergency evacuation checklist; I got out of my seat to open the passenger door and briefed the passengers of the situation. We were able to get both passengers to safety and secure the aircraft on the taxiway. I think the situation was handled well. We shut down the aircraft as fast as we could. The passengers were able to evacuate the aircraft without incident and organization was maintained throughout the event."




Synopsis: C525 First Officer reported a Baggage Smoke annunciation on taxi for takeoff and the Captain elected to stop aircraft operations to have both the passengers and crew safely evacuate the aircraft.
Date: 202104
Local time of day: 1201-1800
Weather elements / visibility: Clear
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Distraction; Situational Awareness; Confusion
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Equipment Issue; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airport; Chart Or Publication; Procedure
Primary problem: Airport

Narrative: Non standard signage. Abdication by ATC to advise hold short of Runway 9C. Jet runway incursion Runway 22R  at Runway 9C.Runway Signage at runway 22R and 9C only indicates Runway 9C. The standard signage should have 27C - 9C. NOTAM the lack of painted holding positions on the runway along with the lack of holding position signage. The Runway 9C sign adjacent Runway 22R is a sign designated by the Aeronautical Information Manual to be a starting position sign. That signage along with the lack of markings fails to designate the runway intersection. In pavement markings and 'WIG WAGS' could have aided in the prevention of this event.




Synopsis: Air Carrier pilot reported a runway incursion due to insufficient  runway and taxiway signage and markings.
Date: 202112
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Aircraft

Narrative: [We] reviewed the log book [and] discussed #2 engine stall momentarily ECAM write-up. Normal push back; engine start and taxi to departure Runway XXR. After takeoff; climbing out of 11000 ft. and accelerating to 280 kts; the #2 engine stalled; EGT went to the red indication. Stopped climb at 12;000 feet. Capt. continued to fly aircraft; Electronic Centralized Aircraft Monitor (ECAM) displayed #2 engine Exhaust Gas Temperature (EGT) exceedance.[Requested priority handling] with departure and requested a return to ZZZ. First Officer was the non-flying pilot; he performed ECAM procedures; Quick Reference Handbook and checklists. We secured the #2 engine. Completed a visual overweight landing to runway XXL. Stopped on runway to have fire department inspect #2 engine. Inspection by fire department was normal. Taxied to gate and deplaned passengers.




Synopsis: A321 Captain reported an engine in flight shut down and air turn back after the #2 engine experienced a re-occurrence of a compressor stall.
Date: 201910
Local time of day: 1801-2400
Location: MCO.Airport, FL
Flight conditions: VMC
Light: Night
Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Taxi
ATC / advisory: Ground MCO
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: I arrived in Orlando International (MCO). After touchdown the Tower instructed me to exit the runway to the right on Taxiway J but I was not able. I was not slow enough to safely exit the runway on J. I replied to the Controller [that I] was not able; and then the Controller asked me to exit to the right on Y which was further ahead. At that time I slowed down the airplane to a speed that would allow me to see and identify the taxiway; so I could safely exit the runway. It was night and I'm not familiar with MCO. I have been there maybe 3 or 4 times in the past 10 years. At that time the Controller instructed me to exit the next taxiway to the left; that I have faster traffic coming behind; so I exited I believe it was B5 or B6; stopped and contacted Ground. The Ground Controller give me a taxi clearance; but I was not able to move because the clearance did not match the taxiway signs around me; and further ahead on the taxiway I saw some vehicles with blinding strobe lights that made the taxiway signs more difficult to see. After a few minutes the Controller sent a vehicle for me to follow to the ramp. In a later conversation over the phone the same night with the Controllers I asked them if I [committed] any violation and they said no; that they just wanted to know what happened. They assured me that there was no violation or damage to anything or anyone that it was just a routine conversation to make sure everything it was ok and if I could tell them what they can improve in that area of the taxiway to make it more visible; because other pilots have been confused with that construction area and signs. Also he said that the Ground Controller was confused about where I was because they cannot see that area of the taxiway where I was from the Tower.




Synopsis: Small aircraft pilot reported being unable to follow taxi instructions due to poor signage and construction at MCO airport.
Date: 202201
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: Marginal
Light: Night
Aircraft: Small Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Horizontal Stabilizer Trim
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Confusion; Distraction; Workload; Situational Awareness; Time Pressure; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Weather
Primary problem: Weather

Narrative: After deicing (TYPE I&IV) application; conducted physical check at gate. Taxied to Runway XXC. Took about 12 minutes. (HOT was 2 hrs). Set icing level to 2. Took off and rotated at Vr. The aircraft started pitch up without normal back pressure and kept pitching up quicker and higher without PF (Pilot Flying) input. Yolk needed to be pushed forward to maintain normal 9 degree pitch. Pitch trim was not responding from both switches on Yolk and STBY. CCAS (Centralized Crew Alerting System) announced icing and selected level 3 at 3000 ft. Hard to maintain altitude and advised ATC to return to ILSXXC. After landing and taxing to[ramp] observed ice accumulation on many aircraft surfaces during post flight. After takeoff rotation; aircraft kept pitching up without PF input.Maintenance suspected that there was ice inside of the pitch trim system. Manually flew aircraft without pitch trim and requested to return to ILSXXC at ZZZ.Should observe all flight control surface movements from outside after deicing application.




Synopsis: Air carrier cargo Captain reported loss of pitch trim control after takeoff. The Captain returned to the departure airport. After a maintenance inspection the cause of the malfunction was suspected to be ice in the control system.
Date: 202007
Local time of day: 0601-1200
Location: DWH.Tower, TX
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Climb
Airspace: Class D DWH
ATC / advisory: Tower DWH
Second aircraft: Other
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
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
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was on a training flight with a student pilot working on pattern work. We were cleared for the option for Runway 17R and instructed to make left closed traffic on the go. ATC cleared a gyrocopter for take off on Runway 17L while we were on short final for Runway 17R. On climb out following the touch and go; the gyrocopter drifted into the extended upwind for Runway 17R. We had to stop our climb and make an evasive turn to the left to avoid collision. After maneuvering to avoid the gyrocopter; we were instructed by ATC to start our left crosswind when able.Given the relatively low speed of the gyrocopter and the proximity of the parallel runways; clearing the gyrocopter for takeoff while we were simultaneously executing a touch and go on the right runway and instructing us to make left closed traffic posed a risk for midair collision. This was further compounded by the gyrocopter drifting into the extended upwind of the parallel runway.




Synopsis: Instructor Pilot reported an NMAC with a gyrocopter in the pattern at DWH airport.
Date: 201405
Flight conditions: IMC
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Human factors: Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Contributing factors: Procedure; Airport
Primary problem: Procedure

Narrative: Taxiing to 22R.  Holding short of E on B.  Ground put an air carrier in front of us and told us to follow them. We followed the air carrier across 22L and Ground got mad.  22L was closed at the time.  Ground said we did not have clearance to cross a runway.  Pretty sure a closed runway is not a runway.




Synopsis: Non-flying pilot follows aircraft but crosses a closed runway without permission.
Date: 201411
Aircraft: No Aircraft
Operator: Air Carrier
Flight phase: Other General Ramp
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Physiological - Other; Troubleshooting; Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Contributing factors: Company Policy; Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: I have several concerns on the handling of assistance devices as some specialty wheelchairs can weigh up to 400 lbs.  Lifting them onto or off the belt loader requires 4 or 5 people to safety lift it.  Once it is on the belt loader there is a concern that it may fall off. (Especially on 757s; Airbuses and wide body aircraft) Getting them to and from the passenger takes a lot of time as elevators and not always readily available.




Synopsis: Reporter describes problems with loading specialty wheelchairs that weigh in up to 400 pounds into an aircraft.
Date: 201506
Local time of day: 0601-1200
Location: SBCW.ARTCC, FO
Flight conditions: VMC
Light: Night
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
ATC / advisory: Center SBCW
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Other / Unknown
Second reporter function: First Officer; Pilot Flying
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: While executing the CGO1A departure from GRU; RW09L; after completing the turn to a 269 track and passing through 3;000 AGL; the aircraft was illuminated by a green laser from almost directly below and to the right of the aircraft.The laser hit the FO (PF) in the right eye and was observed by the CA (PM) and RP on the Flight Deck ceiling. The laser was extremely bright and focused. The FO reported pain and seeing spots in his right eye. Nearly two days later; the FO contacted the CA and informed him that he will seek medical attention as he is still experiencing pain and vision issues from the event. CA informed ATC of the laser attack. ATC ignored the report but the CA wanted the other departing flights on departure frequency to be aware of the event.


Second narrative: On takeoff from GRU at night; I experienced a laser event that affected my eyesight. Partial blindness in my right eye. Laser was very powerful!! It appeared it was tracking all aircraft on the departure because it looked like it was shining on the aircraft ahead of us and then it swung towards us and that is when I looked down and caught it in my vision. We were in a right hand turn which increased my exposure to the laser as it was on our right side and I was the First Officer. I had to get help from the pilot monitoring to fly the aircraft due to my vision degradation.


Synopsis: A B787 flight crew experienced a laser event that partially blinded the First Officer on the initial climb after takeoff. Two days after the event he was still experiencing pain and vision problems and will seek medical help. The Captain reported the event to ATC but was ignored.
Date: 201905
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Rain
Light: Night
Aircraft: Airliner 99
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Cowling
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial
Human factors: Time Pressure; Situational Awareness
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb passing through 9;000 feet precipitation started. The Captain engaged ice protection systems. Shortly after; I noticed sparks and a varying intensity orange glow apparently coming from the #2 engine inlet and surrounding cowling area accompanied by the smell of smoke. No fire annunciations or warnings were observed. I informed the Captain of my observation and I exchanged control of the aircraft back to the Captain. At that time; the Captain made the decision to make an immediate air return. I informed Approach we needed an immediate return. They cleared us for a visual approach and asked if we were declaring an emergency. I informed them that we were [requesting priority handling] and requested fire services be on standby. On descent; I noticed and stated the orange glow and sparks were no longer present. Emergency checklist was discussed and Before Landing checklist was completed. During descent; the Captain requested me to ask ATC for the runway that what was briefed prior to departure. I informed Tower of our request and they promptly cleared us to land. We had a safe landing. We rolled all the way to the end of the runway. We re-verified no sparks or flames as we cleared the runway. We requested fire trucks to follow us all the way to parking at Air Cargo. We completed the After Landing checklist and taxied to the ramp and shut the aircraft down in accordance with the Shutdown checklist. We exited the aircraft and stood a safe distance away while the firefighters conducted an inspection to verify there were no hazards. During this time; we contacted Dispatch and the Chief Pilot. When cleared to approach the aircraft; we noted the engine inlet boot had melted. All procedures were followed as outlined in the SOP.


Second narrative: [Report narrative contained no additional information.]


Synopsis: Beech 99 flight crew reported smelling smoke and observing sparks coming from one of the engines during takeoff and returned to land.
Date: 201509
Local time of day: 1801-2400
Location: ZAN.ARTCC, AK
Aircraft: No Aircraft
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Developmental
Human factors: Human-Machine Interface; Training / Qualification; Workload
Anomaly: ATC Issue All Types
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Provided Assistance; General Flight Cancelled / Delayed
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Flight Data Processers (FDP) backup processor had been out for a couple of weeks (maybe) before this event. FDP has been marked 'intermittent' on our outage sheet. At the time I was receiving a Radar Assist skills check. We overheard another sector telling their supervisor that FDP was not responding. A few minutes later all FDP stations were reporting down and the facility declared a full FDP outage for about 5-10 minutes. This didn't impact my sectors too bad as we weren't busy. If this had happened just a couple hours sooner it would have had an enormous impact on the safety of our sectors.




Synopsis: The Flight Data Processor (FDP) was out of service at this facility. The back-up processor had already been out of service for about two weeks. FDP is how the facility receives; updates and processes all the flight plans automatically. When this is out of service all data must be accomplished manually.
Date: 201509
Local time of day: 1801-2400
Location: MMMX.Airport, FO
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center MMEX
Second aircraft: B747 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: Descending on the AVSAR 3B arrival to [Runway] 23L at MMMX we encountered wake turbulence from a B-747 12 miles ahead on the same arrival. We adjusted our speed and descent rate to avoid any further encounter. A few minutes later we were cleared for the ILS 23L and to caution wake turbulence behind the 747. The following controller told us to turn to a 160 heading to intercept the ILS. I told him I didn't want to cut the turn to the ILS to reduce our wake turbulence separation. He insisted that we turn at that time. We began the turn as requested but at a gradual rate to maintain a safe distance. The wind was out of the east at about 7 kts which would have maintained the wake on the glide slope. We landed uneventfully.




Synopsis: A B737 Captain reported encountering wake turbulence 12 miles in trail of a B747 on approach to MMMX.