elihoole/asrs-aviation-reports huggingface dataset:
Date: 201812
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: Challenger 350
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Fractional
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Deviation - Speed All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Weather
Primary problem: Weather

Narrative: During climb power settings from FL270-FL300 we encountered severe turbulence. Power was immediately reduced to idle power while continuing to climb as well as slowing the aircraft to 250 knots indicated. This encounter occurred in clear air turbulence. The airplane was evaluated by crew to be safe to continue to the destination as a result of no trim required to maintain straight and level flight and there were no Warning messages or faults indicating we hurt the airplane. The autopilot was disengaged momentarily by crew during the event. The owners were checked on shortly after level off at a safe altitude and they appeared unshaken. Normal landing was executed by First Officer.




Synopsis: Challenger 350 Captain reported severe turbulence during climb.
Date: 201302
Local time of day: 1801-2400
Location: TEB.Airport, NJ
Flight conditions: VMC
Light: Dusk
Aircraft: Citation V/Ultra/Encore (C560)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B EWR; Class D TEB
ATC / advisory: TRACON N90
Aircraft component: Autopilot
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Workload
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Overshoot; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Procedure; Chart Or Publication
Primary problem: Ambiguous

Narrative: After takeoff at 1;500 FT AGL; my co-pilot (pilot flying) advised me he was turning on the autopilot. A few seconds later we noticed the airplane was not beginning to level at 2;000 FT per the Teterboro 8 Departure from Runway 1. I advised him that autopilot had not engaged he agreed and leveled the aircraft at 2;040 FT. At that time the aircraft was on a heading of approximately 045 instead of the 040 per the departure. We began the turn to the 280 heading per the SID. At the same time ATC asked us to IDENT and told us to turn left to a heading of 280. I looked at the DME readout from TEB VOR and it said 3.5; the turn was supposed to commence at 2.3 DME. I believe our delayed turn was due to the error in the automation or our failure to engage the auto pilot correctly. ATC had no further comment on our turn.


Second narrative: [No additional information contained in this report.]


Synopsis: A CE560 autopilot did not engage when selected ON while flying the TEB 8 Runway 1 Departure and consequently the aircraft did not level at 2;000 FT nor turn at 2.3 DME.
Date: 201902
Local time of day: 1801-2400
Location: CVG.Airport, KY
Flight conditions: IMC
Weather elements / visibility: .5
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower CVG
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Other / Unknown; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: Upon arrival to CVG [we were] directed to taxi north on taxiway Foxtrot to enter ramp via Taxilane 2N. Ramp was damp and taxi lines were not visible from the flight deck. Captain and I were both outside the aircraft looking to join Taxilane 2N and were unable to discern the lines at night on damp pavement with a fairly dim taxi light. As we moved north; we noted what looked like 18 inch fiberglass small markers sticking up from the concrete and found them right and left of the aircraft. We believed we had passed the taxilane so maneuvered back to the right to proceed east; only to find the aircraft was now over these unlit markers. There was no depiction of these on the taxi diagrams nor was there any note in [company] guidance as to their existence. We were able to return to Taxilane 2N and continued without further incident. Upon arrival at the hotel; we were made aware of a similar issue with crew that landed after our flight. Unlit markers need to be removed or lighted. Reflective blue tape is not sufficient for night visibility. Suggest a comment that these be placed in [company] guidance if not going to be removed.




Synopsis: Air carrier First Officer reported CVG ramp markings in vicinity of Taxilane N2 are poorly lit and difficult to discern in wet conditions.
Date: 201601
Local time of day: 1801-2400
Location: TPA.TRACON, FL
Flight conditions: VMC
Light: Dusk
Aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Operator: Corporate
Operating under: Part 91
Flight plan: VFR
Mission: Utility / Infrastructure
Flight phase: Cruise
Airspace: Class B TPA
ATC / advisory: Tower TPA
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Troubleshooting; Situational Awareness; Human-Machine Interface; Distraction
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Aircraft X was a survey aircraft doing east/west runs over TPA. When the aircraft passed over TPA I noticed that the data block disappeared along with the radar target. This aircraft was in conflict with all TPA downwind traffic and the loss of the track was a major safety risk. When I brought it to the attention to the FLM on duty I was advised that this had happened several times before I took the position.Whatever caused this lapse in radar coverage needs to be addressed to maintain the safety of the NAS. Here at TPA we have been trying to get several STARS (Standard Terminal Automation Replacement System) issues resolved including ghost targets; frequent false starts on aircraft still on the ground and aircraft who have landed reacquiring. These issues increase controller workload and introduce risk into the NAS.




Synopsis: TPA TRACON Controller reported of losing a data block along with the primary target. The aircraft was in conflict with the downwind traffic. Reporter advised the FLM; who told him this had happened several times before he took the position. Controller would like this looked into to avoid it from happening again.
Date: 201908
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach; Descent
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: B747 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Procedure

Narrative: We were on the RNAV Arrival. We had just passed a fix on a 140 track. ATC had cleared us to descend to 6;000 feet from 11;000 feet he then changed the clearance to 9;000 feet. We were behind an [Airline X] flight. Approach turned us to a 200 heading. We could see a B747 at approximately 13;000 feet. The Controller turned us more right. It became clear that the Controller was going to make us follow the B747. We could also hear a [Airline Y] flight behind us on the arrival at 14;000 feet. We were vectored behind both of these aircraft. Progress page was showing us landing with 21.5 at beginning of arrival. Our flight was vectored on to the approach behind [Airline Z]. The Controller left our speed up so we became too close. When we were on about a 3 mile final he made us go around. We went around and were heading back out to sea. I declared minimum fuel. I told the controllers we needed to land now. Our fuel was showing 14.4. They seemed to want to bring us on a long downwind. I told them again we needed to land now. They turned us to join a Visual Approach. We landed with 12.2.I have been flying out of this airport for over XX years. This was the most gross incompetence I have seen in that time. The Air Traffic Controllers did not follow their own rules of first come; first serve. They did not follow their own rules of the lower aircraft had the right of way. They did not provide proper spacing as we were not told to follow the [Airline Z]. They did not coordinate between controllers as with the Approach Controller not knowing why we went around. The next controllers did not seem to know of our fuel state. It was a sad day in ZZZ airspace that could have ended in tragedy. This was on a clear day.




Synopsis: B777 pilot reported they had to go around due to insufficient spacing behind a B747 and landed below their planned fuel remaining.
Date: 201303
Local time of day: 1201-1800
Location: LFPG.Airport, FO
Flight conditions: VMC
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower LFPG
Reporter organization: Air Carrier
Reporter function: Captain; Check Pilot; Pilot Flying
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: When we were Number 1 for take off Runway 09R LFPG; ATC issued the following clearance: 'Air Carrier X; cleared to line up and takeoff'. Having never heard this phraseology before; I asked the LFPG Control Tower if we were 'cleared for takeoff'. The LFPG Control Tower repeated; 'Air Carrier X; cleared to line up and takeoff'. I asked the other 2 pilots (I was pilot flying sitting in the right seat giving an International Qualification to the Captain in the left seat) if they were satisfied that we had received a takeoff clearance and if they felt that it was safe to continue and they both responded in the affirmative. We entered the runway and; as I was advancing the throttles for takeoff; made the following broadcast on the Tower frequency; 'Air Carrier X; rolling Runway 09R'; to which the LFPG Control Tower responded; 'Roger'. The weather was VFR at the time and there were no aircraft downfield waiting to cross our runway. We continued the take off without incident.




Synopsis: Air Carrier departing LFPG was uncertain regarding ATC's 'line up and wait and take off' phraseology; the clearance questioned and take off completed.
Date: 201409
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Caravan 208B
Operator: Air Taxi
Operating under: Part 135
Flight phase: Cruise
Airspace: Class D ZZZ
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: Pre-flight; In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Exposure to toxic fumes and or vapors; TKS fluid. TKS equipped C208 Caravan. Extreme cockpit temperature; 140*+F; TKS fluid in tank in belly pod. TKS aircraft have constant overwhelming chemical odor in heat and pilot noticed on preflight as usual. In flight pilot noticed throat irritation and difficulty breathing; as the Kilfrost TKS 406B MSDS details if exposed to TKS fluid and or its vapors. MSDS warns of danger of vapors in heat. Pilot returned to normal one hour after exiting aircraft. TKS system was not operated. TKS aircraft covered in fluid inside and out permanently and permanent chemical odorMultiple pilots getting sick from TKS system on aircraft. Symptoms incurred by flight crews from being exposed to or breathing TKS fluid; are noted as health warnings on Kilfrost TKS 406B Material Safety Data Sheet. MSDS warns of extreme dangers of repeated exposure.




Synopsis: C208 Captain reports TKS equipped aircraft have a constant overwhelming chemical odor in heat; even when not in use. In flight; the pilot noticed throat irritation and difficulty breathing. The TKS 406B Material Safety Data Sheet warns of extreme dangers of repeated exposure.
Date: 201808
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Champion Citabria Undifferentiated
Operator: Personal
Operating under: Part 91
Flight plan: None
Flight phase: Landing
Airspace: Class G ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Flight Engineer; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control; General Maintenance Action
Contributing factors: Weather
Primary problem: Weather

Narrative: I landed my Citabria at ZZZ. It was a normal wheel landing. The airpark which I live is lined with homes and hangers EXCEPT just a couple of lots; which are still vacant land. After the landing; I was rolling out and slowing down at approximately 15 knots; when I passed by one of the open lots; a gust of wind caught the plane causing it to ground loop. No one was hurt and there was no property damage. The airplane did tip onto its left side causing minor damage.




Synopsis: Citabria pilot reported a wind gust resulting in a ground loop during landing rollout.
Date: 202110
Location: ZZZ.Airport, US
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were towing a B757 on taxiway alpha as the ground ATC cleared us; the direction was tow [Taxiway] 1; 2; hold short [Runway] XXL; as we are towing Gate X is pushing and we did not hear that clear to push on call; I'm watching the other side as airplanes are exiting off the runways; to prepare our tow across the runway. We did not see Gate X pushing until last minute and was a 'near miss;' so last minute we stopped our tow and I was calling ATC for his attention; then he says give way to the push; but that was a little late; he should of said that way earlier; so we pushed our plane back about 20 feet for the push to clear. The ATC had way too much going on to control the ground; landing and takeoffs.




Synopsis: Ground employee reported a ground conflict during pushback and stated communication issues with Ground Control contributed to the event.
Date: 201909
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown; Distraction; Situational Awareness; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Flight Crew Regained Aircraft Control
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Parking brake was not set. Rolled back 5 ft. Captain noticed we were rolling back and set the parking brake. We pulled up to the gate. I grabbed the checklist to start the shutdown checklist. I stated 'parking-brake' 3 times. With no reply. During the event I was focused on the checklist. I stated parking brake 3 times with no reaction from the Captain. Rather than being focused on finishing the checklist I am much more aware of my surroundings. Keeping my head outside the cockpit until the parking brake comes on.




Synopsis: EMB-175 First Officer reported failure to set parking brake at gate.
Date: 201402
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: First Officer
Human factors: Physiological - Other; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight; Taxi
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings; Airport; Human Factors
Primary problem: Airport

Narrative: Over the last few years; the U.S. airport system has been installing extremely bright LED lighting that is blinding to pilots. Most of this is centerline taxiway lighting which; in my opinion; isn't even necessary except in extremely low visibility situations. We can see the painted yellow centerline and the blue edge lights. If there were an animal; FOD; or even a human on the taxiway; we would be quite challenged to see it while blinded by these lights. Some airports have extremely bright approach lights and centerline runway lights as well that also blind us. I have asked ATC if they could lower them and I always get told that they are as low as they go in a frustrated and empathetic tone indicating that they are often requested to lower them.Who decides on the lighting systems installed? Obviously not a user! Most pilots I fly with have issue with this; but everyone just sucks it up and doesn't say anything until we have an incident. If those lights were significantly dimmer wouldn't that save money? Install dimmer bulbs or a dimming system that could go to much lower settings. Don't even use the taxiway centerline lights unless under SMIGS operations. Get feedback from users before installing stuff. Way too bright lighting on taxiway centerline and runway.




Synopsis: B737 First Officer laments the extremely bright LED lights being installed in airports across the country and suggests changes.
Date: 202007
Local time of day: 1801-2400
Location: S56.TRACON, UT
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B SLC
ATC / advisory: TRACON S56
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X in a string for the downwind landing north. I thought I issued 9;000 ft. because the MVA (Minimum Vectoring Altitude) is 8;500 ft. I saw Aircraft X at 8;300 ft. and told them to climb immediately and bungled up the phraseology while attempting a safety alert (which did not go off).  After reviewing the replay; I actually had issued Aircraft X 8;000 ft. I can only assume 8;000 ft. was on my mind because when I base aircraft I give them a heading of 180 and 8;000 ft. I issued the incorrect altitude and attempted to catch it before it was a loss with terrain; but did not. Although multiple things were going on; I should have been more vigilant in my hear-back.




Synopsis: A TRACON Controller reported they mistakenly assigned an aircraft an altitude below the Minimum Vectoring Altitude.