elihoole/asrs-aviation-reports huggingface dataset:
Date: 201902
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: Marginal
Weather elements / visibility: Snow
Light: Daylight
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate; General Flight Cancelled / Delayed
Contributing factors: Weather; Company Policy; Manuals; Procedure
Primary problem: Company Policy

Narrative: Conditions on preflight went from overcast and dry to moderate snow in a matter of minutes. Deicing at ZZZ was thorough and routine; Type I and Type IV; just off the gate with a 20 foot deep pushback.This year's procedure calls for 'Flaps UP' on the Pre Deicing Configuration checklist. This is a change from years past.Reconfiguration checklist performed appropriately.After a short taxi out to Runway 06 for departure; I as the PIC (Pilot in Command); decided to do a 'Cabin Check' to be conservative. Our holdover time was calculated to be 0:30-0:35 minutes so this Cabin Check was NOT required; since moderate snow was falling and we were well under our holdover time.Upon viewing the aircraft wings; there was fully 1 inch of snow on the flaps (which had been lowered AFTER deicing). Snow was accumulated on the entire length of the wingspan on the normally stowed section of the flaps.Flight returned to the gate to re-assess conditions and deice a second time with the flaps selected 'down.'Quite simply; event occurred due to new procedures requiring the flaps to be 'UP' during deicing. Thus the flaps are not treated while the rest of the wing is being treated. In the case of moderate snow or greater; snow will collect on the flaps in violation of the clean control surface requirement for takeoff.It was shocking to me; how fast snow was able to build up on the flaps in this incident. While deicing a second time; we noticed several aircraft from other air carriers deicing with the flaps 'down.'If I had not been proactive and accomplished the pre takeoff cabin check; (which is by its nature uncomfortable for the passengers)...There could have been serious consequences.Highly recommend [the company] re-adopt a flaps down deicing procedure; at the very least during active frozen precipitation.




Synopsis: A319 Captain reported observing snow accumulation on the flaps after de-icing. Returned to gate for second de-icing.
Date: 201604
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: Icing
Light: Daylight
Aircraft: Lancair Evolution
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Autopilot
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was entering route points into the G-900 database as I had received a re-routing. I was flying in and out of IMC weather. My autopilot was not working correctly as it would not hold a vertical or a horizontal path. I was repeatedly manually correcting the deviations with difficulty; having to reset the autopilot in flight. This required aggressively holding the single-arm yoke stick as it tended to deviate left; while putting in the re-routing; with my other hand. Essentially the yoke was frozen at cruise speed; I had little or no ability to do any trimming. Once I landed I called ATC as instructed. I also had mechanics go over the plane and diagnose the problem; which was major; as 3 separate avionics/A&P personnel said I was lucky to be alive. The roll servo's frame or bracket vibrated loose from the frame of the plane thus making the autopilot inoperative as well as any steering extremely hard.The roll servo is attached to the frame of the plane by four screws. One screw was the wrong size. The other three screws vibrated loose and the servo/bracket was resting on the aileron push rods; making contact with the rods. I do not have pictures documenting this mechanical issue. I feel strongly that those planes with the same A/P and roll servo should be alerted to this potential problem. The fix is simple: lift off the back bulkhead and inspect the bracket. Make sure each screw has either lock-tight or a locking nut and the brace/frame is not cracked from the servo's stress.

Callback: The reporter stated that the bracket for the autopilot servo came loose from its mount. The reporter stated that all the early Lancair Evolution with the 'TruTrak' autopilots may have this issue. He would like all owners of this type of aircraft be aware of this problem concerning the installation of the 'TruTrak' autopilots. The reporter claimed that later Lancair Evolution aircraft have Garmin autopilots and do not have the problem with the bracket installation.



Synopsis: A Lancair Evolution pilot reported the autopilot would not hold a vertical or horizontal path. The roll servo's bracket had vibrated loose making steering extremely hard.
Date: 201505
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Other Aerial Survey
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Fuel Distribution System
Component problem: Improperly Operated
Reporter organization: FBO
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On an Aerial Survey mission; at 7;500 MSL (7;400 AGL) the aircraft got low on fuel. My calculations estimated :45 fuel remaining. I had selected one tank so as to assure extra fuel remaining in the other tank. While over the field; the selected tank ran dry.  I then selected 'both' and began an immediate approach. During an extended slip from 7;500 to touchdown; 80 foot field elevation; the engine never restarted. The airplane came to a stop at the exit taxiway.  We pushed it to the fuel island.The field was only 2nm and glide range was at least 12nm.I made the following errors:- I should have landed for fuel when my calculations showed 1hr remaining.- When selecting the 'good tank'; I put the selector on 'both' rather than the single tank.- I should have ensured the forward slip was in the direction of keeping the tank with fuel on the high side; so as to not 'un-port' the tank.Refueling showed that there was only :15 of fuel in the tank.




Synopsis: During an aerial survey flight the pilot of a C-172 miscalculated the fuel remaining. The engine shut down and the pilot landed the aircraft at the destination airport.
Date: 201211
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 40
Light: Daylight
Aircraft: Super King Air 350
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: TRACON ZZZ
Aircraft component: Cockpit Window
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine; Maintenance Powerplant; Maintenance Inspection Authority; Maintenance Airframe
Human factors: Troubleshooting; Training / Qualification; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition; Flight Crew Took Evasive Action; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While level at 9;000 feet; smoke appeared from left glare shield area adjacent to left windshield. Smoke was very pungent and increasing. An emergency was declared with ATC. Pilot flying donned oxygen mask as precaution. Pilot not flying suspected windshield problem and turned OFF windshield heat. After turning windshield heat off; smoke decreased and ceased entirely after a couple of minutes. ATC cleared us to land on Runway 10 and an uneventful landing was made. Maintenance determined a problem with the windshield heat terminal strip; at fault. The windshield heat was placarded inoperative per the MEL; and the aircraft flown to a service center for windshield replacement. This happened on a Beech King Air 350 approximately one year old. Apparently this has happened on other King Airs.




Synopsis: A B350 cockpit windshield heat terminal strip became faulty causing a pungent smoke; so the flying pilot donned oxygen while the non flying pilot turned the windshield heat off; declared an emergency and the flight landed without incident.
Date: 202101
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Distraction; Training / Qualification
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: The rides were bad and Aircraft X asked to descend. My D-side called and requested control; but neglected to point the aircraft out to the underlying sector. I forgot about the shelf as well so I never double checked my D-side's work and I descended the aircraft. There is really no recommendations. The issues are a lack of competency on everyone's part. The D-side barely works as is; and I myself do not get enough quality time anymore because of the lack of traffic. Combined with a constant changing of sector configurations led to this issue.




Synopsis: Center Controller reported descending an aircraft into another Controller's airspace; thinking the D-Side had pointed the aircraft out.
Date: 202012
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Parked pre-departure
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant; Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Police / Security Involved
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: During boarding [I] was notified by Lead Flight Attendant and Customer Service Agent that passengers in row X123 traveling together were loud; intoxicated; disruptive; not adhering to mask policy and one was vaping in his seat. Customer service agent was in the process of removing them when one of them decided to make a display of his anger in the forward part of the aircraft near first class. I was making a cup of coffee and he directed his anger and profanity towards me. I tried to get him to step into the jetway where the other two companions were and hoped he would follow. He mentioned something about getting his jacket and passport but the companions already had them. All three people continued their verbal tirade and protest while the agent called for law enforcement. Subsequent check of their row found two cans of open alcohol containers which they brought on board. Remaining customers seated nearby told the flight attendants they were drinking and loud in the boarding area. Another nearby passenger had been 'egging' them on and also difficult with the agent at check in but he immediately complied with flight attendant instructions; apologized; and said he would not cause any trouble. I discussed this with the customer service agent and told him it was his call whether this passenger be removed as well. Based on his cooperation and lack of evidence of intoxication; he traveled uneventfully on the flight.




Synopsis: Air carrier Captain reported that several intoxicated passengers were being disruptive and not complying with face mask policy. The Captain stated that while one passenger was being removed from the aircraft; he became angry at the Captain and used profanity.
Date: 201204
Local time of day: 1201-1800
Location: RKSI.Airport, FO
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON RKSI
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Distraction; Human-Machine Interface; Situational Awareness; Workload
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Lost both GPS L/R signals on about a 12 mile intercept to final 33R.  Followed the ILS to touchdown and when exiting the runway; both GPS signals came back online. Not knowing what the issue was; an ACARS maintenance record was sent. Two days later; it was made known that GPS signals are being jammed in the area of ICN (RKSI) airport; thus prompting this report.




Synopsis: An air carrier arriving RKSI reported the loss of GPS signals most probably due to jamming so the ILS was flown to touchdown.
Date: 201304
Local time of day: 1201-1800
Location: E80.Airport, NM
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-30 Twin Comanche
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF E80
Second aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Landing on Runway 21 at E80; the AWOS 'preferred runway'. On short final; I saw an airplane departing Runway 3; but had not heard it on CTAF. It was above me and climbing. My rapid descent provided added clearance; but still a near miss. E80 uses a CTAF frequency different than other local airports. In the past; some arrivals have not changed to the correct frequency. We were not on the same frequency. I had not adequately screened the airport for other aircraft. In future: monitor other CTAF's and do a more thorough over flight before landing.




Synopsis: Pilot on short final reports a NMAC with a PA28 departing opposite direction and passing overhead.
Date: 201303
Local time of day: 0001-0600
Location: ZOB.ARTCC, OH
Aircraft: Dash 8-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
ATC / advisory: Center ZOB
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Developmental
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: D-Side Controller issued a clearance direct to the EXTOL Intersection just on the east side of our airspace. I route keyed the aircraft in direct EXTOL it appeared to process correctly; however there have been known issues with the processing using this particular intersection. When I routed in direct using the route key I had not noticed the computer dropped out the Shaff7 arrival to EWR; last I saw on my ACL the aircraft had the arrival. ZBW reported the deviation; they showed the aircraft direct EXTOL direct EWR which was not in fact what the aircraft was doing. I believe the software should at least show us a processing error or some kind of notification if it is going to drop any portion of routing. I also see several times a day where ZBW routes props inbound to CYYZ direct to the LINNG Intersection and the computer drops out the Verko2 arrival; but if I look in the previous route it shows the had the proper arrival.




Synopsis: ZOB Controller described an incorrect routing event when software indicated the correct routing was processing correctly but in fact was dropping out a key route segment.
Date: 201309
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B787 Dreamliner Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Trailing Edge Flap
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cruising at FL400 at mach .855; when the auto throttles started moving back toward idle. EICAS message showed Flaps Drive. We completed the Flaps Drive checklist. Then called Dispatch and talked to Maintenance about the problem. Declared an Emergency and Diverted. We did not dump fuel because this would be under the Max Landing Weight. We made a No Flap landing.




Synopsis: B787 Captain; cruising at FL400 notes autothrottles moving back toward idle and an EICAS message stating Flap Drive. Maintenance is consulted and the flight diverts to a suitable airport for a no flap landing.
Date: 201201
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: Air Conditioning Distribution System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Training / Qualification; Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant; Person Passenger
When detected: Taxi
Result: Flight Crew Returned To Gate; General Physical Injury / Incapacitation; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On taxi out; the Lead Flight Attendant called and reported a 'rotten egg' odor in the rear half of the passenger cabin.  The odor was strong and apparent to all 4 flight attendants and the passengers in the aft half of the cabin.  We returned to the gate for maintenance and while the mechanics were evaluating the systems; paramedics evaluated the flight attendants.  One flight attendant elected to go to the hospital at the paramedics recommendation.  The rest of the crew elected not to.  Maintenance could not duplicate the event at the gate and released the aircraft.  We then ferried the aircraft.  Suspect contamination in Air Conditioning system.




Synopsis: An A321 Captain returned to the gate after taxi out because of a  strong 'rotten egg' smell in the aft aircraft cabin.  One Flight Attendant sought medical attention.