elihoole/asrs-aviation-reports huggingface dataset:
Date: 201709
Local time of day: 1201-1800
Location: HND.Airport, NV
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Beechjet 400
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Final Approach
Airspace: Class D HND
ATC / advisory: Tower HND
Second aircraft: PA-23-250 Aztec
Reporter organization: Corporate
Reporter function: First Officer; Pilot Flying
Reporter qualification: Air Traffic Control Fully Certified; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness
Second reporter function: Captain; Pilot Not Flying
Anomaly: Conflict NMAC
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: Flew into Henderson; Nevada airport. Flew the CLARR3 arrival into the airport followed by a visual approach. Las Vegas approach set us up for 8 mile final then switched us to tower. We flew the visual approach 35L into Henderson. There were three other aircraft on frequency one landing in front of us; one departing and another aircraft joining the left downwind for the parallel runway 35R. When we checked on we were not given the landing clearance; until other aircraft landed and taxi off runway followed by us querying him for landing clearance. We were given clearance 2 miles out. Then we heard an Aztec cleared to join the downwind for 35R. As we approach landing 1 mile out we hear tower querying other aircraft you're clear for left downwind 35R. Tower queries again asking what are you doing then states you're not cleared for base. By that time we noticed the aircraft turning into us. I stopped the descent and begin looking at the incoming aircraft. I looked at our position with the aircraft and runway and as a crew we elected to go around and reenter the traffic pattern for left the downwind 35L. The Aztec aircraft deviated from ATC instructions and clearance. As a crew we responded and acted upon the given circumstances.


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


Synopsis: BE40 flight crew reported a NMAC while on short final to HND with an aircraft that turned base too early.
Date: 201710
Local time of day: 1201-1800
Location: CLT.Airport, NC
Light: Daylight
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B CLT
ATC / advisory: TRACON CLT
Second aircraft: B757 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer
Anomaly: ATC Issue All Types; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: Approaching runway 18R on the localizer near glide slope intercept encountered significant wake turbulence. ATC stated preceding aircraft was a B757 4 miles ahead. Aircraft was temporarily uncontrollable. Autopilot was disconnected and aircraft slowed to minimum approach speed while maintaining flight path above the glide slope.ATC has decided that the previous 5 mile spacing behind B757 aircraft is no longer required when in fact we were vectored too close behind the preceding aircraft to conduct safe operations. Provide the previously required 5 mile spacing behind B757 aircraft.


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


Synopsis: A319 flight crew reported encountering significant wake turbulence on approach to CLT 4.5 miles in trail of a B757. Reporter expressed concern at the reduced separation standards in trail of B757 aircraft.
Date: 201307
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action; Flight Crew Returned To Gate; Flight Crew FLC complied w / Automation / Advisory; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Aircraft

Narrative: After taxi clearance received and after throttles were increased for taxi; I noticed the Number 2 engine had exceeded its EGT parameters. I brought this exceedence to the attention of the Captain who immediately shut off the fuel to the Number 2 engine. Airport Rescue and Fire Fighters inspected Number 2 engine prior to returning to gate. Taxied to gate once they gave us all clear notification. Reviewed QRH. Called for maintenance. Was temporarily distracted from duties as a result of a call from Tower changing our runway assignment. Maintain more vigilance to prevent distractions while performing duties in the cockpit.




Synopsis: A B757 Number 2 EGT exceeded temperature parameters as the throttles were moved to begin taxi so the engine was shutdown; an emergency declared; the QRH completed and the aircraft returned to the gate.
Date: 202007
Aircraft: No Aircraft
Operator: Air Carrier
Flight phase: Other All
Reporter organization: Air Carrier
Reporter function: Gate Agent / CSR; Ramp
Human factors: Situational Awareness; Physiological - Other; Communication Breakdown; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Gate Agent / CSR; Person Ground Personnel
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Company Policy; Human Factors
Primary problem: Company Policy

Narrative: ZZZ break-room not being disinfected and sprayed on a daily basis; as we were told it was going to be. A fellow co-worker has tested positive for COVID and all employees working with this agent have not been properly advised of fellow employee we are working alongside being positive; with symptoms. We had to hear this through the grapevine. And even since agent being confirmed as positive our break-room and back offices have not been properly cleaned.




Synopsis: Airline Ground Agent reported the breakroom is not being sanitized properly for COVID-19.
Date: 202201
Local time of day: 0601-1200
Location: IND.Tower, IN
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Landing
Airspace: Class C IND
ATC / advisory: Tower IND
Aircraft component: Auto Flare
Component problem: Failed; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
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: Environment - Non Weather Related

Narrative: 5G radio interference. At 100 ft. AGL had 'Flare Fail' in heads up display with no flare cue. Altitude call outs were normal. Roll out of 5G telecom. Don't allow 5G telecom near airports!




Synopsis: Pilot reported possible 5G interference on short final landing in IND.
Date: 202101
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: IMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B ZZZ
Aircraft component: Engine Starting System
Component problem: Failed
Reporter organization: Corporate
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Other A&P
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; Flight Crew Regained Aircraft Control; Flight Crew Inflight Shutdown; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were on the ZZZZZ arrival at about 15;000 ft. MSL to ZZZ to cross ZZZZZ at 8;000 [ft.] MSL when the left engine flamed out (failed). We subsequently [advised ATC] and ran the checklist. We had all favorable conditions to restart the engine. The engine airborne restart was successful and we landed at ZZZ without incident.[Company] Mobile Service is in process of repairs. A faulty engine run/stop switch is suspect.




Synopsis: Flight Crew reported engine flameout on short final and continued on to land successfully.
Date: 201309
Local time of day: 0601-1200
Location: CGZ.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operating under: Part 91
Flight phase: Initial Approach
Airspace: Class E CGZ
ATC / advisory: CTAF CGZ
Second aircraft: Skylane 182/RG Turbo Skylane/RG
Reporter function: Instructor; Pilot Not Flying
Human factors: Communication Breakdown
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: While entering left downwind on a 45 entry for Runway 05 at CGZ we almost collided with a high wing Cessna. We had been making radio calls 10 miles out; 5 miles out; 3 mile 45; and entering downwind. While merging in the downwind I (the instructor pilot sitting right seat) looked left one last time and noticed the Cessna climbing above us. I reduced power and kept the Cessna insight; discontinued the traffic pattern. I had attempted multiple radio calls to 'Cessna in the downwind' with no response. Eventually I heard 'Skylane XYZ; radio check.' I confirmed that Skylane XYZ was the aircraft involved in the NMAC and he admitted that he was having radio problems; not able to communicate very well. The G430 had no traffic information on it as we were not in radar contact. Look outside more and do not fly CGZ on heavy traffic days.




Synopsis: PA28 instructor pilot entering the CGZ traffic pattern on the 45 reports a NMAC with a C182 climbing on the downwind. CTAF procedures were in use by the instructor but no reports were received from the C182; whose pilot latter admitted to having radio difficulties.
Date: 201207
Local time of day: 1801-2400
Location: MEM.Airport, TN
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach; Landing
Airspace: Class B MEM
ATC / advisory: Tower MEM
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Weather
Primary problem: Procedure

Narrative: MEM reported wind as 180/10 landing 18L/R. Approximately 40 SW of TAMMY intersection; ATC told us to cross TAMMY at 10;000 indicating a North landing. I told ATC that ATIS was reporting landing to the South. He told us Tower just put out a new ATIS and the weather was the exact same only landing to the North with a strong South wind. When we were handed off to Tower they told us to expect 36L. Because of the tailwind; I requested Runway 09 or 36C the longer of all the North runways; Tower told us unable plan 36L. As we were on final for 36L at 3;000 FT we were showing at 31 KT tailwind. I requested a wind check and we were told 120/15. At approximately 500 FT the wind arrow was indicating a tail wind out of the SE of 19 KTS. At that point; I directed my full attention out side and we may have exceeded the 10 KT tailwind limitation. The landing was normal; maybe a tad long. On rollout I noticed the wind sock was completing extended indicating a strong wind out of the SE. Once clear of the runway; we asked for a wind check and we were told 120/9 which was inconsistent with the wind sock. On taxi-in we pulled a new ATIS and it showed the wind as 120/15g23. Suggestions; my belief is that MEM Tower purposely tries to accommodate the another company operation by landing to the North even when they shouldn't. This is not the first time that this has happened to me; but it is the last! Next time I will declare an emergency; so I can land in the direction that we all should be landing on.




Synopsis: Air Carrier landing MEM voiced concern regarding ATC's accommodation of another operator preferences with regard to runway selection regardless of existing wind conditions.
Date: 201904
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Haze / Smoke; 10
Light: Daylight
Aircraft: Bell Helicopter 407
Operator: Government
Operating under: Part 91
Flight plan: None
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Pilot in Command checked in with ZZZ Tower approximately 9 miles to the north of ZZZ with information Uniform and stating landing was requested at the south high tails (located on west side of field). Pilot in Command was advised to report two miles north. Approximately two miles north of ZZZ; Pilot in Command checked in as instructed. At this point; Pilot in Command was setup to enter a left downwind which would have enabled an approach from the west directly into the south high tails and avoiding the flow of traffic. Tower Controller directed Pilot in Command to fly east of the parallels then enter the south high tails from there. Winds were approximately 020 at 7-10 knots. Pilot in Command complied and was advised by tower that an aircraft was departing [Runway] XXL making a left turn to the southwest. The Pilot in Command believes this is why the Controller made the direction to fly east of the parallels. The Tower Controller advised the aircraft taking off to begin the southwest turn. Pilot in Command observed the aircraft and advised tower he had a visual on the aircraft. The Tower stated another aircraft was also departing [Runway] XXR and would be turning crosswind. At this time; the Pilot in Command was approximately 1/2 mile off the departure end of [Runway] XXR heading to make the east of the parallels entry as directed earlier. The Pilot in Command observed the aircraft climbing off [Runway] XXR making a hard right crosswind turn placing him directly in the path of the Pilot in Command. The Pilot in Command made a hard right turn to avoid the aircraft. At this point; the Pilot in Command came on the radio and stated to the controller that it would have been better to come from the west.




Synopsis: Helicopter pilot reported a NMAC while attempting to land.
Date: 201812
Local time of day: 1201-1800
Location: AVL.Airport, NC
Flight conditions: VMC
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C AVL
ATC / advisory: Tower AVL
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Other / Unknown
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: On approach to KAVL; we received an EGPWS warning. It was day; VMC and positive visual verification found that no obstacle or terrain hazard existed so the warning was regarded as cautionary and the approach was continued; per the [flight manual]. After turning final and descending; flaps 45 was selected at approximately 1000 and the aircraft was stabilized at 500 feet. A normal landing was performed.Rising terrain beneath the aircraft appeared to have triggered the warning based on closure rate. That caused a momentary delay in configuring the aircraft for landing.Due to surrounding terrain; vectors to the final approach course well outside the FAF would have helped to avoid the terrain issue and allowed additional time to configure the aircraft for landing.




Synopsis: Air Carrier First Officer reported EGPWS warning on approach to landing.
Date: 201208
Local time of day: 1801-2400
Location: LCH.Airport, LA
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class E LCH
ATC / advisory: CTAF LCH
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors
Primary problem: Ambiguous

Narrative: Landing in LCH and while crossing the threshold and commencing the flare; the runway lights turned off. The aircraft lighting was sufficient to see the runway and execute a normal landing. At the height the aircraft was at; reaching up to click the mic to turn the lights on would have been a distraction that low to the ground. A go-around on a clear/VMC night where the aircraft's landing lights were illuminating the runway was unnecessary.  A normal landing and clearing of the runway was executed.




Synopsis: EMB-145 Captain reports the runway lights turning off right as the aircraft is in the flare. With sufficient light from landing lights the landing is successfully completed.
Date: 201706
Local time of day: 0001-0600
Location: ZLC.ARTCC, UT
Aircraft: Small Transport
Operator: Corporate
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class E ZLC
ATC / advisory: Center ZLC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
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 Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft; Airspace Structure; Equipment / Tooling
Primary problem: Aircraft

Narrative: Aircraft X checked on my frequency and requested to change destination. I gave the clearance and took mental note that in about 20 minutes he would need a climb to 13000 feet. After about 20 minutes I issued the clearance to climb to 13000 feet with a new altimeter setting with no response. I tried two other transmitters with no acknowledgement. I then relayed through another close by aircraft who got no response. I then tried Aircraft X on guard frequency and to acknowledge with an ident with no response. I then told my Supervisor because I wanted to make sure there wasn't anything else I could try; and to make him aware of the situation. My supervisor had one more idea which we tried along with trying another relay aircraft and guard frequency again. About this time Aircraft X was heard talking on the frequency and was responding to other aircraft and then to me. He was level at 12000 feet and had flown in a 12500 foot MIA (Minimum IFR Altitude) for about 8 minutes and a 12900 foot MIA for about 2 minutes and then into a 13000 foot MIA before getting the clearance to climb to 13000.I'm not sure if this pilot was disconnected somehow or not; but if this was an radio frequency issue maybe there is something that could be done with that. If not; I don't have any recommendations other than me climbing this aircraft when I noticed the eventual need.




Synopsis: A Center Controller observed a NORDO aircraft fly below the minimum IFR Altitudes along their route.