elihoole/asrs-aviation-reports huggingface dataset:
Date: 201909
Local time of day: 1201-1800
Location: DFW.Airport, TX
Flight conditions: VMC
Weather elements / visibility: Turbulence
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E D10
ATC / advisory: TRACON D10
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Crossing Restriction Not Met
Detector: Automation Aircraft RA; Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors; Chart Or Publication; Airspace Structure
Primary problem: Procedure

Narrative: During the BOOVE4 arrival into DFW. We were descending out of 11400 just prior to DELMO for 11000. Approach advised us of traffic at our 1 o'clock climbing. Seconds after; we had a traffic advisory from the TCAS that immediately changed to an RA with a climb advisory. Traffic alerts from ATC and TCAS into DFW occur on almost every arrival and departure. The CA (Captain) responded to the RA immediately; following the guidance. We observed the aircraft pass behind us and low and then continued to descend on the arrival. Seconds later we received another RA on a separate aircraft. This time we were given no advisory by ATC or TCAS. The CA again followed the RA guidance. All the time we were in between clouds. At this point we noticed that during the RA; we were now at approximately 10500 at DELMO. We were then advised by ATC that we were lower than the arrival dictates. We had advised ATC on both occasions of RA. After the situation; it was approximately 10000 before we were able to get the situation under control and start our climb back to 11000. At that point; were given clearance to descend to 6000 and switch frequencies. TCAS and ATC advisories have become a daily occurrence in DFW that I feel should be addressed. After we left for the day (end of trip) the CA was contacted by [Operations Control] and advised that TRACON would like a call about the occurrence. It is rare to get an RA but even more to have two from two separate aircraft within seconds of each other.Traffic congestion in DFW between arrivals and departures. Multiple aircraft in close proximity on ascents and descents.STARs and SIDs should be re-evaluated to not overlap each other in close proximity. Departure aircraft are given 10000 and arrivals are entering the same locations at 11000. The STARs and SIDs have way points that are in very close proximity and with the amount of traffic in DFW; ATC become overworked.




Synopsis: Air Carrier First Officer reported multiple TAs and RAs during approach to DFW.
Date: 201810
Location: IAD.Airport, DC
Flight conditions: IMC
Weather elements / visibility: Windshear; Turbulence; Rain; Thunderstorm
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B IAD
ATC / advisory: Tower IAD
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Speed All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action
Contributing factors: Weather
Primary problem: Weather

Narrative: We had been experiencing continuous light turbulence during our descent on the gibbz2 arrival to Washington Dulles. ATC gave us an initial heads-up that we could expect occasional moderate turbulence. I called the flight attendants and told them to take their jumpseats and that they would have about 5-10 minutes prior to the turbulence beginning. I followed up with a P/A to the passengers and then the turbulence began soon after. We were approximately 1 hour out from IAD. The turbulence never let up; so I called the flight attendants and informed them that it did not appear we would be getting a smooth ride the rest of the way in so they should remain at their jumpseats for the duration of the flight. We sent dispatch a message for the moderate turbulence and they concurred that they had already had several reports of turbulence from other aircraft. We had the radar on and we were actively using both the auto mode and manual to get the best picture of the weather we were dealing with. For the most part we were looking at heavy rain. We were following another [Company] aircraft on the arrival that was approximately 20 miles in front of us. At 6000 feet we heard a [Company] aircraft state they were experiencing hail. ATC never informed us or any of the other aircraft on the radio where that aircraft was. We were actively trying to figure out where the weather that was causing the hail was. The radar was getting a lot of attenuation due to the heavy rain showers. We saw the heavy rain showers about 10 miles ahead and got a turn from ATC but we still experienced severe turbulence +/- 200 feet and +/- 40kts and we were also in light hail for a short time. We informed ATC and they got us turned onto final approach a short time later. We checked with the flight attendants to make sure they were ok in the back and they reported no injuries; everyone was ok. After arriving at the gate we informed maintenance of the severe turbulence and the encounter with hail. There appeared to be no damage to the aircraft but I left before the technician had completed all of their inspections. I also spoke with dispatch on the phone to give a verbal report of the encounter with severe turbulence.




Synopsis: B737 Captain reported encountering severe turbulence and hail during arrival into IAD.
Date: 201909
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew; Person Passenger
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In cruise FL370 approximately ZZZ VOR; Flight Attendant calls cockpit to advise up to 10 passengers around row 38 in cabin all smell electrical burning smell.  Flight Attendant advises they do not smell anything.  I advise Flight Attendant to pay close attention to [the] area and keep me advised. A few minutes later she calls back to advise me that several other passengers are also noticing the same smell and that it is coming and going. At that time; we decide to divert to nearest airport.  We advise Dispatcher and [advised] ATC and diverted to ZZZ.




Synopsis: B737 Captain reported diverting to nearest airport after being advised by a Flight Attendant of growing number of passengers noticing 'electrical burning smell' during cruise.
Date: 201909
Local time of day: 1801-2400
Location: IKV.Airport, IA
Flight conditions: Marginal
Light: Night
Aircraft: TBM 700/TBM 850
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZMP
ATC / advisory: TRACON DSM
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Training / Qualification; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; 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
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: I was working CIC in the TRACON; Developmental released Aircraft X off of Runway 22 at IKV. Developmental assigned Aircraft X a heading of 360 after departure due to traffic landing DSM. The Developmental asked the pilot if this would comply with terrain and obstruction avoidance. The pilot answered affirmative. I told the Developmental that the 360 heading was not a good idea as it will put the aircraft in a 4;000 ft. MSA during IFR/MVFR conditions. Developmental either ignored me or didn't hear apparently. Just because the pilot says he can maintain separation doesn't mean we should be assigning headings towards prominent obstructions; especially when the conditions make it impossible for them to comply. Aircraft X entered a 4;000 ft. MVA at approximately 2;800 ft. prior to passing the altitude of the prominent obstruction. Assign headings away from obstructions for satellite airport departures when it is necessary to assign a heading.




Synopsis: TRACON Controller in Charge [CIC] reported that a Developmental Controller released an aircraft out of a non-towered airport into airspace with a higher MVA against published procedures.
Date: 201810
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: Turbulence; 10
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: 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; Flight Crew Executed Go Around / Missed Approach; Flight Crew Regained Aircraft Control; General Flight Cancelled / Delayed
Contributing factors: Procedure; Weather; Human Factors
Primary problem: Weather

Narrative: We were cleared for the RNAV Approach. As we were approaching a waypoint; and changing to Tower frequency; the Approach Controller gave updated winds to the traffic behind us. The new winds would have been a strong crosswind. We switched to Tower and checked in while we discussed the new winds. We elected to discontinue the approach. While executing the go-around; we were hit by strong turbulence. Tower instructed us to maintain 3000 feet. The Pilot Flying was trying to maintain control and avoid other traffic. In the process we climbed above 3000 feet to approximately 3600 feet. We descended back to 3000 feet and continued to be vectored for the new approach.




Synopsis: B737 First Officer reported exceeding an altitude deviation during a go-around in turbulence and strong winds.
Date: 201903
Local time of day: 0601-1200
Location: OAK.Airport, CA
Aircraft: EMB ERJ 135 ER/LR
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C OAK
ATC / advisory: TRACON NCT
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Private; Flight Crew Commercial
Human factors: Confusion; Distraction; Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: Aircraft X was being vectored to the west for the ILS 12 and was level at 3;200 [feet] and instructed to descend to 3;000 [feet]. This engaged the aircraft GPWS and an aural warning sounded. I began a climb from the assigned altitude of 3;000 [feet] to 3;200 [feet] and informed OAK approach. I descended from there; continuing the approach without conflict.


Second narrative: Upon arriving into OAK; the landing runways were switched from [Runway] 28R to [Runway] 12. We were vectored off of the arrival to be positioned for the ILS 12/visual. At 3;200 feet; we were asked to descend to 3;000 [feet]. Upon descending; we got a terrain warning and landing gear warning. We climbed back up to 3;200 feet to avoid conflict and advised ATC. ATC told us to descend to 3;000 [feet] when able. We complied when clear of conflict and continued on course.


Synopsis: EMB-135 flight crew reported a GPWS event during approach to OAK airport.
Date: 201210
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
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 Executed Go Around / Missed Approach; Flight Crew Landed in Emergency Condition; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While executing a visual approach; we selected 'gear down' and received a 'gear disagree' red CAS/master warning. We immediately recycled the landing gear with the same result. We then executed a missed approach/go around; advised ATC of our situation and the need for vectors to run appropriate checklists. We accomplished the QRH for 'gear disagree' and manually extended the gear. With a gear down and locked indication; we called Maintenance and informed them of our condition. Next; we declared an emergency with ATC and to have emergency equipment standing by; because the QRH read that nose wheel steering may be inoperative after touchdown. We then notified the Flight Attendant of our situation and that; the gear was down and locked; but due to the possibility of no steering after touchdown; we would be executing a brace for landing. Due to the amount of time that all of this took; we had now burned into our reserve fuel; in light of the additional low fuel situation; we put our attention to getting the aircraft on the ground expeditiously. Due to our need set up and quickly brief a different approach; we never had an opportunity to inform the passengers of our situation/plan. We executed the brace at approximately a three mile final. The touchdown and roll out were uneventful. The emergency equipment was dismissed and the passengers were then briefed. Taxi in to the gate was also uneventful.




Synopsis: CRJ200 Captain reports a gear disagree CAS during approach when the gear handle is placed down. A go around is initiated and the gear is extended manually using QRH procedures. An uneventful landing ensues.
Date: 202006
Local time of day: 1801-2400
Location: ZDV.ARTCC, CO
Light: Night
Aircraft: Queen Air 65/70 (Seminole)
Operator: Corporate
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class E ZDV
ATC / advisory: Center ZDV
Aircraft component: Electrical Power
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Pilot Flying
Human factors: Time Pressure; Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [I] encountered smoke in the cockpit from at the time was an unknown source. Immediately started a left hand turn and a descent straight for ITR. Immediately contacted ATC and requested priority handling stating possible electrical fire in cockpit. Continued communication long enough to get airport information and request the fire depatment to be on standby and then shut down electrical systems. I opened the crew hatch to get the smoke from the cabin. Landed. Electrical was turned back on just long enough to extend the gear and then was switched back off. After landing I exited the runway and entered ramp area and shut down immediately keeping the plane a safe distance from fuel pumps. After the engines shut down I evacuated the airplane through the open crew hatch and took safety on the other side of the ramp and then contacted the Director of Operations.




Synopsis: Air taxi pilot reported that smoke in the cockpit resulted in a diversion.
Date: 201604
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B747 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Initial Approach
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuel Crossfeed
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Time Pressure
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Fuel was properly serviced. Somehow; I believe I managed to disable the fuel system logic on the aircraft during preflight and did not receive any EICAS message as to the improper open position of the crossfeed valves until the message low fuel quantity appeared. Override pumps were activated and fuel issue was resolved. Also; as a safety measure; I declared minimum fuel to approach control and we received clearance directly to outer marker fix for normal landing. This was simply because we wanted no delays attached to us during arrival. This was a ferry flight only. Part of our possible distraction was that we were not handled with efficiency at departure station and we were running nearly 1 hour late to start the first leg of a 4 leg charter operation.




Synopsis: B747 Captain reported fuel was correctly loaded onto the aircraft; but the crossfeed valve was left open. Error was not discovered until midflight. Aircrew applied appropriate switches to solve the issue; but still declared minimum fuel into the arrival airport.
Date: 202112
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Rudder Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: 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; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure; MEL; Aircraft
Primary problem: Aircraft

Narrative: Aircraft had RUD TRV LIM 2 deferred. En route we got both a RUD TRV LIM 1 fault and RUD Trim SYS ECAMS enroute.Original deferral said remaining system must work normally. The reported ECAMS countered this and effectively made the deferral moot.Multiple MRMs inbound. Flight left with most signed off referencing the original deferral.Not sure how this aircraft was released.




Synopsis: Captain reported failure of the #1 Rudder Travel Throw Limiter System in flight with the #2 system already deferred causing the Captain to question the airworthiness of the aircraft.
Date: 202005
Location: ZZZ.Airport, US
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: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors; Environment - Non Weather Related; Company Policy
Primary problem: Human Factors

Narrative: Had 2 issues of non-compliance of company policy on same flight:1. None of our catering personnel were wearing a mask while catering our aircraft.2. We had a non-revenue pilot board our flight with required mask on. Then as I observed him from back of aircraft; as soon as he got to his row he took off his mask and put it in his uniform jacket. I came forward and asked him if he needed another mask and he said; 'No; I have one.' I asked him to please put it on. He complied until I walked past him; then took it off again. I mentioned it to our Purser. As she was doing cabin compliance checks with me prior to closing main cabin door; Purser again had to ask him to; 'Please put on mask again.' He complied at that point.




Synopsis: Flight Attendant reported catering personnel were not wearing masks; and a non-revenue pilot was not complying with mask usage until pilot was asked twice to comply.