elihoole/asrs-aviation-reports huggingface dataset:
Date: 201507
Local time of day: 1801-2400
Location: GRR.Airport, MI
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp GRR
Reporter organization: Air Carrier
Reporter function: Captain
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: The taxiway line [ramp] north of Taxiway V in GRR stops as you head northbound around the east side of Concourse B. As you maneuver towards Gates 2 thru 8; you are kind of on your own with regards to clearances; especially from those light poles to your right; same thing as you come around the corner on taxi out until you pick up the taxiway line. Continue the taxiway line north and westbound and into the respective gates.




Synopsis: Air Carrier Captain reports that the Taxiway V center line at GRR ends at the ramp entrance and does not connect to the north bound taxi line around Concourse B.
Date: 202005
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Nosewheel Steering
Component problem: Failed
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: Time Pressure; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Object; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Other Landing
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On landing roll out; we received a 'steering inop' message. We continued to use braking to attempt to stop on the runway; when the aircraft began to drift to the right. We ran the 'Asymmetrical braking' memory items from the QRH; but the aircraft continued away from center line. The aircraft drifted past the runway edge line; struck a runway edge light; and came to a stop on the pavement short of the gravel. No passengers or crew were hurt in the event. Airport maintenance came to tow us from the runway to the gate. Passengers deplaned at the gate without incident. Maintenance did not note any damage to the landing gear. The flight crew and aircraft were removed from duty for the day.The aircraft had a history of 'Steering Inop'; specifically after pushback. The unreliable equipment finally failed at a critical part of the landing roll out. Extra diligence should be used when flying an aircraft with common write ups. Additionally; repeat discrepancies that risk safety of operation possibly should require more attention before releasing to normal operations.




Synopsis: CRJ 700 F/O reported an aircraft with a history of steering problems had a steering failure upon landing causing the aircraft to leave the runway and strike a runway edge light.
Date: 201812
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Rain; Icing
Aircraft: Golden Eagle 421
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Elevator Trim System
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Trim wheel froze in an upward condition at 16;000 feet. Aircraft climbed to 16;300 feet.  Center advised of altitude change; and was advised of troubleshooting in progress.Strong forward pressure was applied to control wheel. Autopilot and trim switches were turned off. Associated circuit breakers were pulled. Power was reduced. Request was granted for descent to 6;000 feet. Approaching descent altitude; trim wheel became operative. Approach and landing were made normally.




Synopsis: C421 Captain reported a frozen elevator trim resulted in the aircraft overshooting an altitude restriction by 300 feet. The flight crew disconnected the autopilot and ATC provided assistance clearing the crew to descend where the trim became operative.
Date: 201210
Local time of day: 1201-1800
Location: ZBW.ARTCC, NH
Flight conditions: VMC
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZBW
ATC / advisory: Center ZBW
Aircraft component: Traffic Collision Avoidance System (TCAS)
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Aircraft

Narrative: We were level at FL290 with a clearance to cross BUOYY at FL240.  We had not started down when we observed a TCAS target approaching the aircraft 1700 feet below us and climbing towards us.  We stayed level as it climbed to with 900 feet of our altitude and came within approximately 1.5 miles to our right hand side.  We decided to question Boston center about the traffic as we had been cleared to descend to FL240.  I asked if they were talking to the traffic climbing toward us from below and they said only that they were talking to a B777 descending towards us from above.  Both myself; and the First Officer are sure the TCAS was displaying a climbing target.  Also the First Officer is sure he saw two separate targets; one climbing towards us and one descending towards us.  Boston Center had no observed target where we claimed one to be.  When we landed we were given a phone number and asked to call the Center.  I spoke with two different managers; including three separate calls with the QC manager for Boston Center.  He seemed very concerned as they had no known target on their radar and he also indicated 'something similar had happened a week or so ago in the north of their sector' I called Maintenance Control on his behalf; and asked if the aircraft saved TCAS information.  Maintenance spoke with 'Safety' and I was told that no; the aircraft does not save TCAS information.




Synopsis: EMB170 Captain describes a TCAS target climbing towards his aircraft after having received a descent clearance.  When ATC is questioned they reply that there is no target at that location and altitude.
Date: 201205
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Antiskid System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Troubleshooting; Situational Awareness; Communication Breakdown; Distraction
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other My Co-worker(s) discovered it
Result: General Maintenance Action
Contributing factors: Procedure; Manuals; Logbook Entry; Human Factors; Chart Or Publication; Aircraft
Primary problem: Human Factors

Narrative: Aircraft X set out with Anti-Skid Control box along with Stores Parts Compatibility List and Maintenance Manual. Installed box to see if problem would be fixed; followed Maintenance Manual for trouble shooting with no help. Moved Aircraft X to [Ramp] pad and went back to Shop to gather more information and talk about what we wanted to do next. [I] talked about installing everything back to original. Troubleshoot for eight hours; found two problems; fixed them but failed to double check with my Partner that the original [Anti-Skid Control] box was back in Aircraft X and failed to document Anti-Skid was installed for troubleshooting. Also did not verify Serial Number on [Parts] Tag for new Anti-Skid box. [Recommend] verifying that the original box is in the aircraft [and] make sure to document the removal of component for the aircraft.




Synopsis: A Line Mechanic failed to properly document on a Non-Routine write-up that he had removed an Anti-Skid Control box and installed a new box in an aircraft for troubleshooting purposes. The new box was not removed due to a lack of adequate communication between himself and another Mechanic.
Date: 201510
Local time of day: 0601-1200
Location: CLT.Airport, NC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZTL
ATC / advisory: Center ZTL
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Chart Or Publication; Procedure
Primary problem: Procedure

Narrative: ATC giving changes to a new STAR Arrival into CLT; To cross BACKK below 14;000 ft [FILPZ1]. BACKK published restrictions of FL190-12;000 ft. We are 5;000 ft high from what FMS has planned. We have already started our arrival descent and with not enough time to reprogram system. Auto Pilot OFF; Speed Brakes Out; Dive to make restriction. WHY? Two days earlier on IVANE got MAYOS at FL220 with very short notice. A/P OFF and Dive to make restriction. This must stop happening! We did not have an Altitude Deviation but this should not be normal business practice in CLT!These changes are happening in CLT all too often. Please change STAR to what is needed for an arrival (Isn't this the reason for a STAR?) These last minute changes have to stop or I will stop accepting STARS or refuse to stay on a STAR with these kinds of requests. I hope you can feel my frustration in this matter. I'm too old to keep putting up with this stuff. I would be happy to help someone get this changed.




Synopsis: A320 Captain laments frequent ATC changes to RNAV arrival crossing restrictions requiring the use of speed brakes and defeating the purpose of the OPD.
Date: 202105
Local time of day: 1801-2400
Location: RNT.Airport, WA
Light: Night
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D RNT
Second aircraft: Small Transport
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other Landing Rollout
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During approach to landing at RNT; winds were light; 360 at 3kts. We chose to land on Runway 34; during our landing I noticed bright lights at the end of the runway heading towards us. I immediately turned the aircraft towards the nearest taxiway and made a radio call. I got no answer and Aircraft Y took off from Runway 16 above us apparently oblivious to the fact that we just landed on the opposite runway at the same time they departed. Tower was closed. I went back and listened to the ATC audio from the landing and you can hear Aircraft Y make a departure call that I didn't hear. Then you hear all my calls; downwind base and final. The Aircraft Y makes another radio call again that we did not receive then we make a call from the ground once I saw the Aircraft Y rolling towards us. The Aircraft Y started it's takeoff roll on Runway 16 as we landed on Runway 34. I checked the radio after and our radio is functional; able to transmit and receive.




Synopsis: Pilot reported a ground conflict occurred during landing rollout when another aircraft took off from the opposite end of the runway.
Date: 202110
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: APU Fuel System
Component problem: Malfunctioning
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: Situational Awareness; Troubleshooting; Communication Breakdown
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Fuel Issue
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Pushback operator alerted us to a fuel leak at the center of the fuselage. Maintenance was called. Maintenance asked for an immediate APU shutdown. No power on aircraft. Fuel odor and fumes filled the cabin. I asked the A Flight Attendant to initiate an Emergency Deplanement. She did. Passengers returned to terminal. Maintenance fixed the leak signed the book and we re-boarded and departed. The Mechanic seemed pretty serious about shutting down the APU and left with no other input. Given the information I was presented with I would react the same again.




Synopsis: A321 Captain reported that push back operator advised that a fuel leak was present on aircraft belly.
Date: 201503
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: Mixed
Weather elements / visibility: 10
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Human-Machine Interface; Communication Breakdown; Distraction
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA; Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Company Policy

Narrative: The flight was the first leg of a three-day trip. We had just departed Runway 27R on the RNAV Departure with a clearance to 10;000 Feet. We checked in with Departure Control and were told 'delete the 250 knot speed restriction.' We were then given a climb to 14;000 Feet and contact Center. We read back the altitude and frequency and switched to Center. We were then cleared to climb to FL240. Moments later we received a TCAS Alert and complied with its commands. We questioned ATC as to what happened and they switched us back to Departure Control. Departure Control informed us that we had mistakenly taken another aircraft's altitude clearance and frequency change. We continued on to ZZZ and called ATC upon landing. The Supervisor gave us an explanation as to what had happened. The Departure Controller had given a climb clearance and frequency change in the same transmission which he said they shouldn't do. The clearance we had taken was meant for the aircraft in front of us on the same departure.Flying out of this airport is busy enough. But flying an older model aircraft just adds to the workload. No auto throttles; no map display; etc. I feel these planes should be base specific like we did with the old pre-FMS aircraft back in the day.


Second narrative: The mixing of old and new technology aircraft has put my margin of risk very high. In 17 years of 121 flying; this is the first time I have ever had this type of error.


Synopsis: A flight crew flying a less automated aircraft than they were accustomed to and somewhat overloaded; took another aircraft's clearance which resulted in a TCAS alert along with a call to ATC.
Date: 201808
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Air/Ground Communication
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; Flight Crew Landed As Precaution; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [Aircraft] was on departure for ZZZ1 airport on the filed IFR plan. At around 800 feet. AGL I noticed that the radios got silent. I continued the upwind and started to troubleshoot loss of radio communications (checked circuit breakers; recycled the avionics master; tried comm 2; tried the hand held microphone mounted in the aircraft) and then squawked 7600 from the initial transponder code. I then turned crosswind then downwind of RWY XXL of ZZZ then tried to deploy flaps and it was set but did not indicate. I then extended the landing gear saw one over my shoulder and one in the mirror. I checked to see if the RWY (Runway) was clear and it was; I then reduced to the approach speed of 85 KIAS. I was able to land comfortably. After getting on the ground I was unable to easily keep directional control and I gave it as much right rudder and brakes as possible. In order to stop as safely as possible. I saw the XX taxiway and attempted to make it however; I could only stop in the grass between RWY XXL and taxiway XX.




Synopsis: Cessna 210 pilot reported that on departure lost all communication; returned and lost directional control of the aircraft upon landing.
Date: 201903
Local time of day: 0601-1200
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: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance; Inflight Event / Encounter Fuel Issue
Detector: Person Dispatch
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Per the recommendation of a previous [report]; I was concerned that the crew for flight XXX would add fuel creating a weight restriction and possibly an overweight aircraft via the pilot mobile fuel add; so I added the remark please call Dispatch prior to adding fuel.The crew unilaterally added fuel via the pilot mobile application without calling Dispatch per the condition of the flight release. I contend that this is a violation of FAR 121.533 as I have no way to restrict this functionality allowing the pilot unilateral decision making over the preflight planning of a flight.




Synopsis: Dispatcher reported being out of the loop when a flight crew unilaterally added fuel to the aircraft by using a mobile fuel application.
Date: 201705
Aircraft: B747 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Aircraft component: Tablet
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: During flight; I was trying to look at the map on the iPad to get info and while trying to close in on the area; it froze up and I could not change the picture to get the information I wanted. Also after landing; my iPad does not switch to the taxi diagram even though it is selected and this time it had timed out so when I was given complicated taxi directions after getting clear of the runway; my iPad wasn't available and I had to rely totally on the First Officer's for directions.




Synopsis: B747 Captain reported iPad malfunctions in flight and during taxi.
Date: 201701
Local time of day: 1201-1800
Location: ZZZ.Airport, US
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 E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: GPWS
Component problem: Design; Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Airport; Procedure
Primary problem: Ambiguous

Narrative: I was Pilot Flying; when cleared by Approach to descend to 3000. Received an altitude alert; and responded by executing escape maneuver. Not sure if the aircraft terrain database is off; my descent was too steep (1000 fpm); or what. There was no imminent terrain threat; and we were cleared down by ATC. Executed climb to approximately 3800 feet and notified ATC that we were responding to an altitude alert. Eventually descended again back to 3000. I would likely just attempt a more shallow descent if given the same instructions in that area to see if that was why the alert occurred.




Synopsis: EMB145 First Officer reported a terrain warning after being cleared by Approach to descend to 3000 feet. Evasive action was taken; but no reason for the warning could be found.