elihoole/asrs-aviation-reports huggingface dataset:
Date: 201402
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Intake Ice System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Relief Pilot; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: On climbout the Captain tried to engage the engine anti-ice. The Left Engine Valve light in the button remained on and the accompanying L-ENG Anti-Ice EICAS Message was displayed. After checking the enroute and destination weather conditions; we determined the engine anti-ice was required for the flight. We decided to return and declared an emergency for the overweight landing. I checked the climb limited landing weight and the runway limited landing weights as per the overweight landing procedure in the QRH. We determined the landing performance weights were not a factor. The Captain elected to make a flaps 25 landing. The touchdown was very smooth. VVI at TD was 100-200 FPM down. Reverse thrust only was used to stop the aircraft. A visual inspection of the brakes was made by ARFF after clearing the runway. Brakes were determined to be 'cold to the touch' by ARFF. The emergency was terminated and we taxied to the gate normally.




Synopsis: B757 First Officer reports engine anti-ice valve failure to open during climb. With a long flight ahead and icing conditions in the forecast; the crew elects to return to the departure airport for an overweight landing.
Date: 201908
Local time of day: 0601-1200
Location: PHL.Airport, PA
Light: Dawn
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B PHL
ATC / advisory: Tower PHL
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Aircraft

Narrative: We were on the ILS Z 9R going into PHL this morning. I picked up the approach lights right at minimums; and a few seconds later Tower told us to go around because the aircraft in front of us was still on the runway. We never saw anything beyond the runway threshold before we executed the go around. ATC notified us to go around right before we landed. The aircraft that landed in front of us was still on the runway. We immediately executed the go around; came back around with approach; and landed on our second attempt.




Synopsis: EMB-145 Captain reported Tower commanded a go-around just before landing at PHL because the preceding aircraft was still on the runway.
Date: 202112
Aircraft: B737 MAX 9
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: AC Generator/Alternator
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: During my walk around; I noticed some oil on the outboard thrust reverser. I opened the IDG service panel and noticed that the #1 Engine IDG oil level was not visible through the sight glass. I serviced the IDG and accomplished a 5 min idle run. No leaks were noted.While accomplishing the ETOPS PDSC; I noticed that the #1 Engine has oil stain on the outboard thrust reverser. I opened up the IDG service panel and noticed that the IDG had no oil quantity visible in the sight glass.. I serviced the IDG and accomplished a 5 min. Idle run. No leaks were noted. I added 2 qts.




Synopsis: Technician reported finding oil on the thrust reverser during an ETOPS PDSC and serviced the #1 IDG with two quarts of oil.
Date: 201511
Local time of day: 0601-1200
Location: LAX.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground LAX
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We called for push; Ground said it would be a while; another carrier was pushing in alley. We finally received clearance to push. While starting the number two engine; Ground said expect 24L; which we had in box. While starting the number one engine; Ground said expect 25R; due to VIP movement. FO continued start while I went into the performance computer to get numbers for that runway. After we programmed the new data; Ground said if we can taxi immediately we could get 24L again. Once again we went into the performance computer to change data; and started to taxi. We forgot to do the before taxi checklist. Caught on taxi out when did throttle check; and got horn since we didn't put out flaps. At that time put flaps out and ran before taxi checklist; and then before takeoff checklist.




Synopsis: B737-700 Captain reported taxiing without running the before taxi checklist when they were distracted by multiple departure runway changes.
Date: 201303
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Powerplant Lubrication System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Diverted; Flight Crew Inflight Shutdown; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Oil pressure and oil quantity went to zero at cruise [with a] rapid rise in EGT. [We] shutdown the engine and diverted off our oceanic track and returned to our departure airport.




Synopsis: When it was necessary to shut down one engine due to zero oil pressure and quantity; a B757 flight crew diverged from their oceanic track and returned to their departure airport.
Date: 201212
Local time of day: 0001-0600
Location: ZAU.ARTCC, IL
Aircraft: Falcon 900
Flight plan: IFR
Flight phase: Descent
Airspace: Class A ZAU
ATC / advisory: Center ZAU
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Other / Unknown
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Aircraft X was preceding direct HALIE direct MDW; descending to cross 60 miles East of HALIE at FL240. When Aircraft X was roughly 20 miles West of FWA; I noticed Aircraft X was in coast track; with no altitude read out. There was a Mode C intruder beneath the data block; showing FL296. I asked Aircraft X to report his altitude; and the data block disappeared; I was left with only a Mode C intruder; and the Mode C intruder showed a transponder code one digit off from Aircraft X's code. I tried to start a track; got some ridiculous fail message; I told Aircraft X  to reset his transponder; tried to start a track again; got a ridiculous fail message; coordinated with the two surrounding sectors (LOGAN and BEARZ) and then Aircraft X's data block reappeared. The LOGAN Controller was one of our ERAM SMEs and he said since the (incorrect) code is not recognized; ERAM will not display a data block. I recommend we fall back to HOST immediately. Fortunately; all my attention was directed at Aircraft X while the episode occurred. Had my attention been directed elsewhere; it may have been some time before I recognized I was missing a crucial data block; that I had a Mode C intruder; and the issue needed to be corrected by reassigning Aircraft X the appropriate beacon code. For a data block to randomly drop off is unsafe. Controllers deserve a better system.




Synopsis: ZAU Controller voiced concern regarding an ERAM dropped data block; recommending a return to the HOST RADAR system.
Date: 201905
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: SA-227 AC Metro III
Operator: Air Carrier
Flight plan: IFR
Flight phase: Takeoff / Launch
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
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: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: My nose wheel steering was deferred. I taxied to the runway using differential power and braking. I started to execute a normal takeoff and something didn't feel right with the power. I can't describe it but it just didn't feel right. I aborted the take off. I had aborted before getting a good look at the engines. I pulled off the taxiway and in the run-up area and brought the power up to see if I could recreate the issue while not moving. The engines proceeded to run fine. I then notified Tower that I was ready to try to takeoff again. I started to execute the takeoff and noticed it was pulling to the left. I started to add left power until I could hold as straight as I could. I looked down at the torque gauges and saw I had a significant amount of differential power (left engine was at 80-90 and the right was down at 20.) I immediately executed a second abort. This time the plane went hard over to the left; skidded on the runway; and then went into the grass; taking out a taxiway sign. I immediately shut both the engines down and ATC sent the response team.I think I would've been able to keep the airplane on the runway if the nose wheel steering wasn't deferred. It had been worked on in the past week and the mechanic deferred it after replacing some parts.




Synopsis: SA227 Captain reported a runway excursion resulted when directional control was lost due to low torque on the right engine and deferred nose wheel steering.
Date: 201402
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Dusk
Aircraft: Beech 1900
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Aircraft component: Cowling
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Ambiguous

Narrative: I was the First Officer for roundtrip flights. Prior to operating the roundtrip; I was the Captain on the inbound flight that arrived 38 minutes prior to the departure of the roundtrip. As I got to the aircraft; the Captain was already doing the preflight walk-around. We finished the rest of our preflight duties and departed on time. In the turn around station; I did the post-flight walk-around and found no discrepancies. Back in original airport; I once again did the walk-around in the late afternoon. Once again; I found no discrepancies. Sunset was approaching and light was waning; but not so much as to need a flashlight. I do distinctly remember looking in the engine inlets during both of the walk-arounds I performed. The next day I was notified of the inlet plugs that had been found in the engine that morning. I was not there in the morning to know what events lead up to the plugs being sucked into the engine. That would be the first place to try to find a cause and preventative recourse. I'm not sure if I didn't look close enough in the inlets; or if the plugs were not in sight. I do believe that if the plugs were brightly colored; they would have not been missed on at least 6 different walk-arounds by 4 different people.




Synopsis: A BE-1900 First Officer reported doing several preflight walk-arounds; including looking in the engine inlets; and not seeing inlet covers which had been ingested during that aircraft's first start at the originating station.
Date: 201703
Local time of day: 0001-0600
Location: UTSD.ARTCC, FO
Aircraft: Gulfstream G650
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Flight phase: Cruise
ATC / advisory: Center UTSD
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: This is to report an ATC incident flying on airway A466 in cruise and level at FL430 while approaching intersection AMDAR (which is on the northern FIR boundary of Afghanistan). The normal procedure is to call ahead 10 minutes prior to the Afghanistan boundary for entry permission.I have flown this route many times previously. The Controller has always been an American equipped with a strong and clear radio. On [this flight;] on initial contact I was answered by a male with a heavy accent using a weak radio and instructed to descend to 'thirty thousand' (not the correct phraseology - [should have been] 'flight level 300'). I refused the instruction saying we could climb if traffic was the issue. A few moments afterward the 'real' controller came on saying 'disregard'; maintain FL430; verify squawk and report position AMDAR.So be careful for bogus ATC instructions approaching the Afghanistan FIRs.




Synopsis: G650 pilot reported contact with an apparent interloper issuing bogus ATC clearances on the Afghanistan FIR frequency.
Date: 201907
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Dassault-Breguet Undifferentiated or Other Model
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Corporate
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
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 Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were on leg 3 of 3 for the day. The first two legs we noticed a strong smell like something burning. It would come and go; so it was hard to determine where the odor was coming from. On the third leg the smell got considerably stronger. The PNF [Pilot not Flying] went to check the cabin and return to the cockpit. Upon return; the PNF commented that the smell was concentrated in the cockpit and no smell was apparent in the cabin or galley. Also; on troubleshooting; the PF [Pilot Flying] noticed that the smell was not coming out of the gaspers. ATC gave us a clearance to descent for our arrival into our destination. Shortly after; grey/white smoke/fumes started illuminating from the lower center panel windscreen. We [notified] ATC and asked for a diversion to ZZZ. The crew donned masks. The PNF coordinated with ATC lower altitude and a direct flight path to the final approach fix for RWY XXR at ZZZ. The smoke continued for about 2 minutes then ceased. We removed our masks and returned to headsets thinking the smoke was stopped. About 2 minutes later; the smoke returned; requiring us to return to the mask operation. The smoke continued for about another 2 minutes before stopping. The rest of the flight until landing was operated on headsets. A stable approach was conducted with the priority handling from ATC. A normal landing was performed; taxied off the active runway. Emergency services were standing by to assist if needed. They followed us to the ramp to check on the passengers; crew; and aircraft. No further assistance was required. The FA [Flight Attendant] took initiative and took care of the passengers watching the cues from the cockpit. After the first occurrence of smoke; the crew notified the FA 10 minutes to landing. On the second occurrence of smoke in the cockpit; the FA directed the passengers to don smoke hoods.




Synopsis: First Officer reported strong burning fumes during cruise which turned to smoke. Flight crew executed a divert and completed an uneventful landing.
Date: 201205
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 9
Light: Daylight
Aircraft: Citation V/Ultra/Encore (C560)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Navigational Equipment and Processing
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Distraction; Troubleshooting; Human-Machine Interface; Situational Awareness; Time Pressure
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Aircraft Equipment Problem Dissipated; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I departed and had to switch over to symbol #2 generator to get navigation system to track to GPS route. Was on IFR vectors to localizer when I realized none of my IFR approach options were working. So we were in VFR conditions and I saw the airport and canceled IFR. Started VFR approach and contacted Tower. Was told to cancel all restrictions and cleared to land. Knowing the area very well; I stayed in visual contact with airport and landed. After landing called Maintenance and told them of the lock up I had on the navigation system. After the systems were shut down I ordered GPU hook up and turned avionics back on and everything was working. I have never seen this happen before I thought I had symbol generator #1 problem and when we switched to #2 it all worked and we continued our flight. We left for two leg flight the next day everything worked. I have ordered another computer system that operates most all autopilot and NAV systems. Whatever locked up the system somehow corrected its condition when power was removed after shut down. I had a lot of VFR options for landing at other airports; but having a visual contact with my destination made the most sense. Having back up systems are great but having the kind of lock up in the NAV system changes the landing options to VFR only. Knowing the system the way I do; some sort of electronic lock up occurred and may never happen again but replacing the main computer system should prevent it from ever happening again.




Synopsis: A CE560 Symbol Generator #1 malfunctioned in flight; disabling navigation systems. After landing all systems returned to normal after they were shutdown and restarted.
Date: 201303
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Weather elements / visibility: Turbulence
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Weather
Primary problem: Weather

Narrative: Twenty minutes into the flight; reaching FL370; and on top of the last cloud layer; we encountered turbulence that became severe. Wind shear plus up and down drafts activated the shaker momentarily disconnecting the autopilot. First Officer maintained level attitude and second shaker activation followed; there were just seconds between the two shaker activations. We descended with a downdraft 3;500 feet leveling at FL330. All this time; we were in contact with Center and I notified them of our inability to maintain altitude.




Synopsis: ERJ-170 Captain reported stick shaker and inability to maintain altitude at FL370 in severe turbulence.