elihoole/asrs-aviation-reports huggingface dataset:
Date: 201907
Local time of day: 0601-1200
Location: DEN.Airport, CO
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B DEN
ATC / advisory: TRACON D01
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Inflight Event / Encounter Wake Vortex Encounter
Detector: Automation Aircraft RA
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Procedure
Primary problem: Procedure

Narrative: On LOC to 16L at 9000 ft; parallel traffic above and converging. Approach [advised] there was traffic; but we did not acknowledge in sight. [We received an] RA (Resolution Advisory) as we became parallel to 16R traffic. Followed RA to descend; but able to stay on approach. Approach was notified. Wake turbulence from previous aircraft to 16L. Second time recently with the exact same issue of RA.




Synopsis: B737NG Captain reported responding to a Resolution Advisory for an airborne conflict on arrival into DEN.
Date: 201508
Local time of day: 1801-2400
Location: GRB.TRACON, WI
Weather elements / visibility: Fog; Haze / Smoke; 0
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E GRB
ATC / advisory: TRACON GRB
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Situational Awareness; Troubleshooting; Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Regained Aircraft Control; Flight Crew Overcame Equipment Problem; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors; Weather
Primary problem: Human Factors

Narrative: Error message indicating loss of Number 1 GPS connection. Auto select back-up GPS Number 2 (loss degrades approach capability). While trouble shooting the error inadvertently pulled the AHRS (Air Heading Reference System) breaker and lost Primary Flight Display (PFD) altitude; heading and attitude indicator.Distracted by the loss of information and still trying to trouble shoot the GPS failure and in solid IFR conditions there was a brief loss of control.  The aircraft lost over 1;000 feet and 90 degrees of heading before I recognized the problem and using back-up instruments began correcting. The entire episode lasted about 2 minutes.I contacted ATC as soon as I recognized the loss of control but the controller misunderstood and thought I was asking for a new routing? Eventually we reinstated our fight plan clearance.




Synopsis: SR22T pilot reported heading and altitude deviations associated with loss of control during troubleshooting of a GPS problem.
Date: 201908
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
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: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was assigned to operate flight to ZZZ. I was the Pilot In Command and was the Pilot Monitoring during this flight. While on the STAR going into ZZZ; we just passed through approximately 19;000 feet MSL. At that time; my First Officer and I both looked at each other and asked if we smelled something. Both of us agreed that it smelled like a wet or dirty sock in the flight deck. Based on other information I have received from other pilots flying this type of aircraft; and other types of aircraft; I assumed it was potentially a fumes event we were experiencing. I immediately pulled my quick donning oxygen mask out and donned it. I called back to the flight attendants and asked if they smelled anything unusual to which they both said no. At that time and knowing that PACK 1 generally supplies air to the flight deck and based on our altitude of approximately 16;000 feet MSL; I told my First Officer I was going to turn PACK 1 off; to which I did. We continued the descent and after approximately 3 minutes; I took my mask off to see if I could smell the odor anymore; to which I could not. I told my First Officer that we will continue with the arrival and approach and once we land; we will write up the airplane; to which I later did. The remainder of the arrival and approach was conducted without further incident and no emergencies were declared. Based on these continual and potential fumes events; I highly recommend that [Company] along with other airlines; develop a QRC checklist for these type of odors.




Synopsis: EMB-175 Captain reported a 'dirty socks' odor during arrival. Odor dissipated after turning Pack 1 off.
Date: 201509
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Fuel System
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Human Factors

Narrative: While being fueled I first noticed that the fueler fueled the left wing first; which triggered a fuel imbalanced ECAM. Then he fueled the right wing. Then he fueled the AFT ACT (Additional Center Tank) with 850 lbs; then the FWD ACT with 175 lbs. Because there was fuel in the AFT ACT with the forward not full (working with our dispatcher); we called the fueler back to the aircraft to fill the FWD ACT tank; causing a departure delay. At the first waypoint check we found that the FWD ACT fuel (5000 lbs) was trapped and not burning. Again working with our dispatcher; we continued on to our destination. At the gate we inspected the aircraft wing fuel panel to find 4 of the fuel panel switches in the wrong position.




Synopsis: A321 Captain reported that the Fueler did not reposition switches correctly in the wing fuel panel which resulted in trapped fuel in the forward ACT (Additional Center Tank).
Date: 201208
Local time of day: 1201-1800
Location: NHK.Airport, MD
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower NHK
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown; Workload; Situational Awareness; Confusion
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Airport; Human Factors
Primary problem: Ambiguous

Narrative: Under positive control from the Tower; I taxied on Alpha west from the ramp. The taxiway to the convergence of Runways 02 and 06 passes through a restricted zone encompassing the national command aircraft; a restricted area where (I was warned) the use of deadly force is authorized in the event of vehicles traversing the area come to a halt. Immediately after passing these armed guards; I crossed three feet over the hold short line for the Runway (06) I was to depart on and stopped approximately 75 to 100 yards from the runway. I confused the line I breached with the hold short line for the closer Runway (02) but both converge at the same point and there was only one hold short line. I requested a 180; but had already fouled the deck necessitating a go-around by a landing aircraft. At the time of the incident; my aircraft's position was clearly marked and visible to me on GPS airport maps by Garmin and Avidyne but the error still obtained. I should have requested a progressive taxi; but was speaking to the Tower while crossing through the restricted zone. I did not turn back to see whether the signage was clear; but obviously; this was my responsibility.




Synopsis: A pilot failed to detect the hold short for NHK Runways 2 and 6 because it was so distant from the common runway entry point. An aircraft on final approach was issued a go around clearance.
Date: 202103
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Multiengine
Human factors: Training / Qualification
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft ground-looped on landing damaging landing gear; prop and wingtip.




Synopsis: Pilot of a biplane reported loss of directional control on landing that resulted in a ground loop and some aircraft damage.
Date: 201811
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 5
Light: Daylight
Aircraft: PA-46 Malibu Meridian
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Landing
Airspace: Class C ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Hydraulic System
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were coming in for approach on Runway XX. When we hit the glideslope; I put the gear down and flaps 10; but the gear horn kept sounding and the gear light would not extinguish. I slowed down to flap speeds and further dropped the flaps. Approximately 500 feet AGL; we executed a go-around to troubleshoot.When I retracted the flaps with the flap lever; the flaps wouldn't retract. We reset the circuit breakers for the gear and the flaps but neither was working. We then pulled the emergency gear release at 90 knots; but the gear horn kept going off and the gear light still didn't extinguish. We were on a left downwind at that time and tried to porpoise and fishtail the plane but that didn't seem to work either.We started smelling and seeing smoke come out of the pilot-side circuit breakers; so we pulled into a left base to final and landed on the belly.




Synopsis: PA-46 pilot reported the flaps failed to retract and landing gear failed to extend fully; resulting in a gear up landing. Additionally; smoke appeared behind the pilot side circuit breakers.
Date: 201408
Location: ZZZ.ARTCC, US
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZ
Aircraft component: Recirculation Fan
Component problem: Malfunctioning
Reporter function: Pilot Not Flying; First Officer
Human factors: Workload; Situational Awareness
Second reporter function: Captain; Pilot Flying
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 FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action; General Declared Emergency; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Due to smoke in cockpit. Detected smoke in cockpit. [ATC] recleared [us] to our destination. Emergency evacuation accomplished.


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

Second callback: The Captain stated that when maintenance examined the aircraft they found the recirculation fan motor bearing had failed which caused the smoke.

Synopsis: An EMB-145 crew reported detecting smoke in the cockpit; and diverting to a nearby airport. A recirculation fan bearing had failed.
Date: 201205
Local time of day: 0601-1200
Location: BOS.Airport, MA
Flight conditions: IMC
Weather elements / visibility: 1
Aircraft: No Aircraft
Flight phase: Taxi
ATC / advisory: Tower BOS
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: The Airport vehicle was doing his usual daily airport inspection for bird activity. Weather was IFR; visibility >1 and ceiling about 200 FT. Vehicle notified me he was stopping for a moment near the approach end of Runway 4R. There was an aircraft on about a three mile final to that runway. The CIC and I noticed; using binoculars; that the vehicle driver was shooting flares in the direction of the oncoming aircraft. Not only were the flares a potential hazard; but if the birds lying in the grass were agitated; they would be in flight low level at the approach end of the runway while the arriving aircraft was short final. I have continuously asked the facility to address the issue of airport vehicles and their movement on the airport. There seems to be a lack of understanding of air traffic operations. This is an acute example. Vehicle operators need to be aware of what they're doing and how it may impact the safety of aircraft. Birds sitting in the grass are much less a hazard than getting those birds to commence flight off the ground while an aircraft if flaring on arrival to an adjacent runway less than 100 FT away. It would be beneficial for airport operators to discuss these issues with the controllers they regularly communicate with; rather than having points of contact who are staff that have not worked traffic in the tower in several years. Bird inspections and dispersal of birds should be done when there is NO activity on the airport; not when the traffic is starting up for the day. In no case should flares be shot towards an oncoming arrival aircraft.




Synopsis: A BOS Controller voiced concern regarding bird activity actions taken by an airport vehicle operator that was potentially unsafe. The reporter suggests airport employees be given training regarding this issue.
Date: 201511
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: SA-227 AC Metro III
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Taxi
Aircraft component: Main Gear
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Maintenance
When detected: Taxi
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Flight went as planned. It was a ferry flight [that] was to be conducted with the gear to remain down and locked for the duration of the flight. There were no abnormal indications in the cockpit throughout the flight. All three landing gear position indicators indicated down and locked for the entire duration of the flight. After landing the airplane was taxied to the hangar for parking where the engines were shut down and airplane was secured per the aircraft checklists. The landing gear also indicated down and locked during the taxi from after landing to parking. The airplane was then hooked up to a tug where the aircraft began to be pushed back into the hangar with a towbar. The right main gear then collapsed as it was being pushed back. I have no knowledge of why this may have happened. A thorough preflight was conducted prior to flight using the aircraft checklist which included an inspection of the right main landing gear and gear well. No abnormalities were noted or detected. Throughout the entire duration of the flight and also after landing at our destination; the landing gear position indicators indicated all three landing gear were down and locked.


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


Synopsis: SA-227 flight crew reported that following an uneventful ferry flight the right main landing gear collapsed while the aircraft was being backed into the hangar by a tug.
Date: 201512
Local time of day: 1801-2400
Location: LAX.Airport, CA
Flight conditions: VMC
Light: Night
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Ground LAX
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification
Anomaly: Conflict Ground Conflict; Less Severe; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Taxiing into [ramp parking] spot at LAX. We had [another] airplane directly in front of us as we taxied in. The preceding aircraft had moved far enough down the lane to allow us to follow them in safely. As I was taxiing through the throat; two fuel trucks were observed by myself and the first officer to be driving past the preceding airplane on the active taxiway. From what I could tell; the aircraft in front of us was still under its own power and the tug had not yet had a chance to hook up to the aircraft. The trucks were; at best; over-anxious to move past them. After they passed the aircraft in front of us they continued toward us while I was still actively taxiing. Both trucks were squarely in the taxi lane with no part of their vehicles was on the proper side of the taxiway clearance lines. I had to bring my aircraft to a halt because the trucks were driving toward my left wing without clearance while in the taxiway. The trucks then stopped; on the active taxiway; abeam the cockpit of my aircraft. The smaller of the two; which had been following the first larger truck; apparently understood the need to get off the taxiway and he went around the large truck to get out of the way. The larger truck sat on the taxiway; blocking our progress for about two minutes. Repeated flashing of the runway turnoff lights finally got him to get off of the taxiway.The operators of these trucks had little; if any; respect for aircraft priority on taxiways. I have not seen something this blatant in ground operations in 30 years of flying. Please work with this fueler to bring their operators within the rules for ground ops. Lack of proper training for fuel truck operators. Retraining of the personnel involved; and restating of the policies to other drivers in the employer's workforce.




Synopsis: MD-11 Captain reported a fuel truck did not follow proper procedures and interfered with his taxi on the ramp at LAX.
Date: 202110
Aircraft: Medium Transport
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 Multiengine; Flight Crew Instrument
Human factors: Fatigue
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Work Refused
Contributing factors: Company Policy; Human Factors
Primary problem: Company Policy

Narrative: After working 5 consecutive days with a five leg day on day 4 with only a 10.5 hour rest period the night before and after just completing a 4 leg 9 hour day; I was junior manned. I did not feel alert or rested enough to accept the extension of my planned duty time; especially considering that it would have created a 7 day conflict with my next sequence.Cause - Staffing and Weather; ZZZ had long weather delays before my duty day had even started and was declared [non-normal operations]. The high winds and resulting weather made for a longer and more stressful day and I was very tired by the end. The bigger problem is the constant under staffing of the Captains on the Medium Transport aircraft in ZZZ. Junior manning should not be the only staffing solution; but it is! Every question above on this report is exasperated by the constant junior manning that we have experienced for the past X months.




Synopsis: Air carrier Captain reported fatigue due to long; consecutive days of flying and cited weather and staffing as contributing factors.