elihoole/asrs-aviation-reports huggingface dataset:
Date: 201508
Local time of day: 1201-1800
Location: EGLL.Airport, FO
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
ATC / advisory: Tower EGLL
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Procedure; Weather
Primary problem: Ambiguous

Narrative: EGLL RWY 27R; stable approach to 250 feet AGL. Due wind gusts: at 250 feet AGL a loss of 8 kts airspeed with corresponding pitch attitude change. Auto-throttle engaged and system unable to rapidly correct deteriorating airspeed. Aiding the Auto-throttle system; I initially manually applied considerable power. Subsequent total loss of 12 - 14 kts at 150 feet AGL. Pushed throttles up to TOGA and pressed TOGA switch. Preformed successful manual go-around followed by auto-pilot engaged at 900 feet AGL. Engaged LNAV and VNAV.Missed approach procedures: First Officer advised me that a 185 kt speed limit (in a turn) may have been exceeded. I am unaware of speed exceedance during the 'turning portion' of this missed approach. Accelerated to clean maneuver speed during straight (non-turning) portion of this event. I could not find the initial (185kts) missed approach turning speed assignment on EGLL chart 11-4.  This event bordered on Low Level windshear.




Synopsis: A B777 Captain is advised by his First Officer that a 185 kt speed limit (in a turn) may have been exceeded during a missed approach at EGLL due windshear. This limit cannot be found anywhere on the 11-4 Approach chart.
Date: 201811
Local time of day: 0601-1200
Location: TKI.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E D10
ATC / advisory: Tower TKI
Second aircraft: Commercial Fixed Wing
Reporter organization: Personal
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Riding passenger with a 100 hour pilot; VFR. Inbound airliner passed about 1000 ft above us maybe 1/2 NM ahead of us; perpendicular to our path. I believe we were not talking to ATC any more as we had just crossed through TKI airspace and were not handed off to approach or center. I believe we had started out with VFR flight following [enroute to ZZZ]. It's been a few months and I don't remember fully; so it is possible we simply squawked VFR and informed McKinney Tower as we transited their airspace. As we spotted the traffic; we noted on the sectional that we were right near the jetways that come in to DFW and Love; so we didn't think seeing the airliner was unusual; and we had experience with the Class Bravo airspace with lots of air traffic. The air was cool; smooth; and stable. As we crossed the path where the jet had just been; we noticed a very slight bit of turbulence. It rocked our wings a little but didn't even amount to light turbulence; and it was momentary. We remarked that it was most likely the wake turbulence from the jet. It stopped; then we noticed it again; but more slight. Our pilot remarked that it was from the other wing. I said; 'maybe tail'; and then we encountered the turbulence from the other wing; which was slightly stronger again; matching the other wing. The only reason I'm filing this report is I noticed that NASA was soliciting reports of wake turbulence encounters from GA pilots. If there had been any other turbulence at all; we never would have known we passed through wake turbulence.




Synopsis: PA-28 pilot reported encountering wake turbulence from an air carrier aircraft in the vicinity of TKI airport.
Date: 201412
Local time of day: 0601-1200
Flight conditions: IMC
Weather elements / visibility: Icing
Light: Daylight
Aircraft: Caravan 208B
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Flight phase: Parked
Aircraft component: De-Icing Fluid
Component problem: Improperly Operated
Reporter organization: Air Taxi
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Commercial
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Inflight Event / Encounter Weather / Turbulence
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Procedure
Primary problem: Procedure

Narrative: We took aircraft the aircraft round trip. We were in and out of IMC both there and back. Temperature was above freezing on first leg; but on return we momentarily picked up some trace ice. De-ice system was activated normally per the company SOP and aircraft POH. System was only used in the normal position for a few minutes. Later that afternoon while preparing to take the same aircraft for another flight; I was informed that glycol was added to the TKS fluid tank. Neither the captain nor myself had knowledge of this prior to departing and only became aware later that afternoon.




Synopsis: A C208 crew was informed after flight in icing conditions that the aircraft's TKS system was mistakenly serviced with glycol instead of the authorized fluid.
Date: 202004
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Human factors: Distraction
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other Post Flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Due to COVID-19 I had not been home in over a month. I work in ZZZ but live in a different state. I'm at risk at work so did not come home. Finally got a long stretch of days off and needed to fly my airplane. I had not seen my family for a long time. With no body flying I thought it would be a good chance be able to fly over there house. So I told them I was flying over if I could. ZZZ1 said they had a 40 minute gap with no traffic and I could fly over. I found their house and they were out side. After that we flew to another city.After we got back I got thinking about the flight and I realized I had probably exceeded the normal bank angle and I was not in a rural area. I did my normal planning but had not really thought about what it entailed once I got there. My ADM [Aeronautical Decision Making] was lacking in my preflight planning. I thought about the flight but not what was going to happen when I got there. Thought we will wave take a picture and leave. But there was more to it than that. I needed to think about the process once we got there other than we will just wave and take a picture. Just poor planning for that part of the flight.




Synopsis: GA pilot reported a flight over homes may have been too low.
Date: 201808
Location: ZZZ.Airport, US
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed
Contributing factors: Human Factors; Company Policy
Primary problem: Human Factors

Narrative: After briefing FA (Flight Attendant) I inspected crew meals. There was no dry ice in galley cart. FO (First Officer) meal was cold and with his plan to eat early he was fine. My meal was warm and I deemed it spoiled. Catering came took temperature and at 67 degrees agreed it was spoiled. Eventually a replacement meal and dry ice was provided. During the process I was greeted by a retired pilot and then subsequently a call by [Chief Pilot] due to me delaying flight to get a crew meal replacement. Both were friendly and not overtly pushing; but the mere presence and phone call implied pushing. Safety is priority. Just like a crew plans a route and fuel to safely conduct a flight; I also include my meal plan for the day to fuel me. I expect catering to provide the meals ordered so my plan can be safely executed. Had I not inspected the meals consuming a spoiled me further not refrigerated by dry ice 3 hours after departure and 4 plus after a spoiled meal was boarded a food poisoning event was a serious threat. To have two management types get involved and have station blame delay on me rather than root cause that catering failed; smacks of pushing and is contrary to safety. I don't like delaying flights. I take pride in serving our customers on time; but my health and safety should not be questioned or pushed.




Synopsis: B757 Captain reported an issue with the crew meals.
Date: 202004
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Weather elements / visibility: Thunderstorm; 50
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Company Policy; Weather; Human Factors; Environment - Non Weather Related
Primary problem: Weather

Narrative: Flight from ZZZ to ZZZ1 in an overwater equipped aircraft with a co-pilot that hasn't completed overwater training. We were on a filed route that kept us close to the shoreline but had to deviate around area of heavy thunderstorms which got us farther off shore than authorized by our ops specs. I filed the flight [plan]; but didn't take into account that any deviation further offshore would exceed acceptable distance from the shoreline. Due to COVID-19 my co-pilot's overwater training had been cancelled and that fact I hadn't considered when I filed the flight plan. I will definitely review everyone's quals in the future and be sure the filed route complies with all regulations.




Synopsis: Air taxi pilot reported that while deviating around thunderstorms; the track resulted in flying farther offshore than allowed by company Ops Specs. The pilot noted that due to COVID-19 the co-pilot's overwater training had been cancelled.
Date: 201808
Location: NFFF.ARTCC, FO
Flight conditions: VMC
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: Relief Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Weather
Primary problem: Weather

Narrative: I was the [Relief Pilot]. Captain and First Officer were on break. We received a severe turbulence segment on our outs of flight from FL240 to FL410. Requested deviation below which was denied and then to offset laterally 150 miles; but only given 120 miles. We considered weather deviation without a clearance procedures as well as declaring an [urgent situation]. As Captain was awake in the seat; and had requested we wake him in prior briefing should an event like this be considered; he came up to flight deck. I then sat in Observer's seat. He had [another Relief Pilot] CPDLC to ATC that we would be deviating to the lat/long of outer most point of severe turbulence segment which was a 148 offset. As this was not our clearance; I suggested the weather deviation without a clearance procedure as well as possibility of declaring an [urgent situation]. We had just been cleared from FL400 to FL390 while preceding on the south offset. The Captain did not want to go up or down 300 feet with the decency of the altitude clearance. We turned on all lights and broadcast our position and intentions on both 121.5 and 124.45. We talked to Dispatch on SAT comm. We reached Nadi Radio who said we were only cleared to offset 120 miles and we were at 148 miles. We received the same message over CPDLC. I spoke with Nadi Radio and said we were given no other options as we were flying through an area of forecast severe turbulence. We were then given a clearance through Nadi Radio to deviate up to 148 miles and received the same on CPDLC.




Synopsis: Air carrier First Officer reported needing to deviate around an area of forecast severe turbulence and was unable to get complete clearance to do so.
Date: 201601
Location: ZZZ.ARTCC, FO
Weather elements / visibility: Turbulence
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General Physical Injury / Incapacitation
Contributing factors: Weather
Primary problem: Weather

Narrative: At cruise altitude of FL350 ATC reported moderate turbulence ahead between FL330 and FL290. FL270 recommended as a good altitude. I turned on the 'fasten seat belt sign'; and made a PA to be seated. The first officer began descent to FL270. During the descent I made a PA for the flight attendants to be seated. After leveling at FL270 for about 5 minutes and with a smooth ride I phoned flight attendants to resume duties but left the seat belt sign on.At XA:51 encountered severe turbulence at FL270 with a duration of 15 seconds. After event number one flight attendant reported three injuries. Two flight attendants and one passenger who was in the aft lavatory. Decision made to continue to destination. Medical personnel met flight and attended to the three who were involved.




Synopsis: Air carrier Captain reported they encountered a brief period of severe turbulence at a reportedly smooth altitude. Three people were injured.
Date: 201209
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Human factors: Workload; Other / Unknown; Distraction
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented; General Evacuated; General Maintenance Action
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: After evacuating the aircraft on a taxiway due to smoke in the cockpit and cabin; neither the Captain nor I wrote-up the aircraft in the maintenance log. We forgot due to being very busy dealing with the aftermath of the emergency that had just occurred. A major threat was task saturation. The company; fire department; and station personnel were constantly calling us; asking us questions; and having us complete paperwork for several hours after the emergency.




Synopsis: CRJ-700 First Officer reports evacuating the aircraft during taxi due to smoke in the cockpit and cabin. The crew is informed a day later that no logbook entry was made.
Date: 201410
Local time of day: 1801-2400
Location: DEN.Airport, CO
Light: Night
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Airspace: Class B DEN
ATC / advisory: TRACON D01
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Confusion; Distraction; Situational Awareness; Training / Qualification; Troubleshooting; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure; ATC Equipment / Nav Facility / Buildings
Primary problem: Procedure

Narrative: During an busy arrival rush weather caused a sudden shift from Visual Approaches to Triple Simultaneous ILS approaches.  We do this a lot at Denver and should be no problem.  The new STARS RADAR and lack of training caused several losses of legal separation and safety issues.  Several controllers were rapidly shuffled from on position to another to open the MO positions.  Position relief briefing were instructed to be short and the 2 minute overlap was waived.  The MO positions were not 'opened' and the controllers were unable to look at and data blocks and therefore could not open.  The controllers and the FLM did not know how to fix the situation due to lack of training and understanding.  Luckily a 'SME' happened to be in the room and even they struggled to get the position working.  About half a dozen aircraft illegally flew an unmonitored; side-by-side; ILS approach.  The TM-in-training (and soon to be FLM) thought that nothing was wrong with the operation.The training for STARS has caused hundreds of problems that have been logged and many more that have not.  Everything from not being able to amend and aircraft's type to the RADAR scope turning off entirely are causing safety problems that do not seem to be taken seriously.  It seems like 'they'll figure it out' was a huge part of unveiling STARS.  This is dangerous and today proved that.  Better training and equipment fixes are needed.




Synopsis: D01 Controller reports of problems associated with STARS equipment not working correctly and having aircraft on final with less than standard separation.
Date: 201508
Local time of day: 0001-0600
Location: CLT.TRACON, NC
Flight conditions: IMC
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E CLT
ATC / advisory: TRACON CLT
Aircraft component: Tablet
Component problem: Design; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Distraction
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Approaching MAJIC; Atlanta Center instructed us to descend via the IVANE 5. As I read back the clearance; my iPad mount came unattached from the window and fell on my arm. This began my distraction from the flight; as I started reattaching my iPad and bracket to the window. Sometime after MAJIC (now with CLT Approach;) we were told to slow to 210; turn left; and descend to 7;000. After that; the controller asked if we were given a descend via clearance; as we seemed kind of low. I responded yes; and then looked at our altitude. We were passing through 9;000 feet. I was then aware I had not been paying attention to our descent profile and was not sure if we missed a crossing altitude earlier on the arrival. I did NOT ask the controller if we had missed any altitudes. As I was unaware of any deviations; I am submitting this as a precaution.First; get Electronic Flight Bag (EFB) hard mounts. Second; I should not have allowed myself to become so distracted by re-attaching my EFB mount. In the future; I will allow it to stay 'dislodged' until we are in a safe environment to reconnect it.


Second narrative: I have had the Electronic Flight Bag (EFB) mounts fall on my arm several times. Not only is it startling; but in some cases hurts my arm if it falls a certain way. Luckily it hasn't fallen during the takeoff roll; but I imagine that would be the scariest time for it to fall (or perhaps during the flare in a landing). The EFB mounts are a simple remedy to a potentially serious disruption in the cockpit.


Synopsis: ERJ-175 flight crew reported they had a possible altitude deviation on approach to CLT when they were distracted by the Captain's iPad mount coming loose and falling onto his arm.