elihoole/asrs-aviation-reports huggingface dataset:
Date: 201506
Location: DEN.Airport, CO
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi; Parked
ATC / advisory: Ramp DEN
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors; Company Policy
Primary problem: Company Policy

Narrative: Gate was not prepared to timely receive our flight in an APU OFF configuration as mandated by company procedure. The ground power cable was not pre-positioned for our gate arrival and an estimated 4 minutes elapsed from setting the parking brake to getting ground electrics established. There was no attempt by ramp personnel to establish power until after the jetway was attached and main cabin door open facilitating passenger deplanement; which I was extremely uncomfortable continuing with our number 1 engine still running. Ramp personnel first attempted to connect the wrong cable to our aircraft further delaying the process.I was extremely uncomfortable with this delay and made the decision to start the aircraft APU after approximately 1 minute after gate arrival as it was immediately apparent that the ground personnel had not adequately and safely prepared for our APU OFF arrival and I did not feel it safe to continue the gate arrival process with number 1 engine running for this extended time.




Synopsis: B737 Captain reported new company procedure calling for no APU start on taxi in are causing some safety concerns.
Date: 201508
Local time of day: 1801-2400
Location: PHX.Airport, AZ
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower PHX
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Prior to the Top of Descent; the FO calculated the fuel burn and subtracted it from the current weight on the INIT/REF page. All normal so far. Then; he punched the calculated weight into both the performance computer and the FMC. He made a math error that I did not catch when reviewing the data. On final; the aircraft did not feel right. [It felt] sluggish and 'burbly.' I quickly hit the INIT/REF page to double-check the 30 flap speeds. Here's the problem. The weight that he punched into the FMC was still there - 111.8. That's about 20;000 pounds too light for the 737-800 we were flying. There was no way for me to double-check the speeds. I knew the speeds were wrong and flew fast to compensate. The landing was normal. He is not the first FO I've flown with that manually changes the aircraft weight in the FMC. By doing this; we gain nothing and lose the ability to double-check the speeds with the calculated data.




Synopsis: B737-800 Captain experiences a math error by his First Officer during approach speed calculations. The weight used is 20;000 pounds too light and the slow approach speed that results is detected by the feel of the aircraft.
Date: 202008
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
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: Distraction; Situational Awareness
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: ZZZZZ2 Departure to ZZZZZ at 4;000 feet.  Max airspeed at ZZZZZ1 230 kts; restriction loaded in FMS and briefed. Light aircraft with high climb performance; PF became concerned FD and AT commands would cause difficult level off.  Lowered pitch below FD command bar to correct which resulted in acceleration; PF thought VNAV and AT weren't complying restriction and began to reduce thrust.  PM commanded correction to FD pitch and proper speed; but during correction speed accelerated above 230 kts to approximately 250 kts momentarily before correcting to 230 kts.  Improper pitch and power for VNAV guidance and flight conditions. Proper understanding of how VNAV modes handle restrictions and good briefing of anticipated modes and performance beforehand.




Synopsis: Air carrier Captain reported a speed deviation during departure.
Date: 201807
Local time of day: 0601-1200
Location: ZAU.ARTCC, IL
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna Single Piston Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class B ORD
ATC / advisory: TRACON C90
Second aircraft: Amateur/Home Built/Experimental
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Was in contact with flight following; Chicago ATC. Aircraft Y passed opposite direction on right side within 200 feet. ATC warned of the target 4 miles out; then 2 miles. My passenger is a pilot and we were both looking; but did not see Aircraft Y until it was upon us.Very scary. Do not have a good solution; except that Aircraft Y did not appear to be in communication with ATC and therefore did not know our whereabouts. Yes; ADS-B will help when installed.Next time will stay further offshore so will not get pinched closer to the shoreline where traffic is most likely to be. Raises another issue with being too far from the shore in case of an engine failure.




Synopsis: GA pilot reported an NMAC with an experimental aircraft that was not in communication with ATC.
Date: 202011
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Workload; Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant; Person Passenger
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Passengers seated in [row] XX [seats] 2345 were instructed several times by Flight Attendant C to keep their face coverings on at all times. They continued to disregard her request. Please put them in our no fly list. They are the type of passengers that will never follow our travel requirements.




Synopsis: Flight Attendant reported a group of passengers would not comply with face mask policy.
Date: 201604
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: Military Trainer
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Fire/Overheat Warning
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Human factors: Situational Awareness; Distraction; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Airspace Violation All Types; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Exited Penetrated Airspace; Flight Crew Inflight Shutdown; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Departure Airport
Contributing factors: Human Factors; Airspace Structure; Aircraft
Primary problem: Human Factors

Narrative: I was flying with a student when we started to have problems with one engine. We had a fire warning intermittent and we had to shut down the right engine. When I was reading and perform[ing] all the checklists; the student who was not familiar with the area; instead of staying on the left of the power lines; went on the right of the power lines entering in the [Restricted Airspace].After restarting the engine inflight and regaining control of the airplane; I turned immediately away from the [Restricted Airspace] at 90 degrees angle; and after landing back in [departure] airport; TRACON called me and asked me to call [another airport] tower for a possible pilot violation. I called right away; explained them what happened and the gentleman talked with his supervisor and he said that they would not report a pilot violation and discussed how to prevent another occurrence.




Synopsis: The pilot of a small military style jet trainer reported an airspace violation occurred while addressing an engine fire warning problem.
Date: 201708
Local time of day: 0601-1200
Location: HEF.Airport, VA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Citation II/SP (C551)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Takeoff / Launch
ATC / advisory: Tower HEF
Aircraft component: Elevator Trim System
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Procedure; Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Immediately after rotation the pitch trim forces on the aircraft required nose up trim. When nose up trim was applied a nose down pitching force was encountered. Upon further application of up trim a more pronounced nose down force was encountered. Both the pic and sic applied back pressure on the control column to overcome the nose down tendency. A close in flat pattern was flown and the aircraft landed uneventfully.Maintenance had rigged the trim actuator on the tail backwards. Neither the shop technicians nor the flight crew caught this error until a flight was attempted.In future this pilot will perform a full flight control and trim control check of any aircraft coming out of maintenance personally.




Synopsis: Pilot of Cessna Citation II reported the pitch trim was functioning in opposite direction to intended input.
Date: 201402
Local time of day: 1801-2400
Location: BUF.Airport, NY
Flight conditions: VMC
Weather elements / visibility: Rain; 6
Aircraft: EMB ERJ 135 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight phase: Initial Approach
Airspace: Class C BUF
ATC / advisory: TRACON BUF
Aircraft component: ILS/VOR
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Localizer signal unreliable/intermittent. On approach into BUF; we received an intermittent and unreliable signal for Runway 05. We acknowledged the NOTAM that coupled approaches were not allowed for the ILS 05. The First Officer hand flew the approach as we intercepted the LOC; 5 miles outside of ZOBSO. At 3 miles outside of ZOBSO; our CDI showed a red X; indicating that we lost the signal. After about 2 seconds; it came back and we recaptured and continued the approach. Moments later at ZOBSO; we lost LOC signal again. This time I conferred with First Officer and said we should consider abandoning the approach and try something else. He concurred and we told ATC of our issues of the signal reception. He stated the current weather and pointed out the airport to us; that we can continue visually. We discussed our options; saw the airport straight ahead and continued our approach visually. I monitored the LOC signal as we continued. The signal was lost two more times and when we did receive the signal; it swung back and forth in an unreliable manner. After landing; we relayed to the tower that we had issues with the localizer signal. The airplane was not written-up as we had used the localizer at LGA 22 and CLE 24L and it worked correctly. This LOC signal has a history of issues. I have written previous reports for GRR 26L; LGA 04. Another LOC with reliability issues is LEX 22.




Synopsis: EMB-135 Captain finds the localizer for Runway 05 at BUF to be unacceptable even though it is NOTAMed to prohibit coupled approaches. Other airport localizers are cited as not being well received by aircraft that he flies.
Date: 201811
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach; Landing; Taxi
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Government
Reporter function: Other / Unknown
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
When detected: In-flight; Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was on break and got a call from a TRACON Controller that the Controller in the Cab was experiencing some kind of medical episode. I ran upstairs to check on the Controller and saw that the Controller was unable to continue to work. There were many aircraft holding on the ground at the ramp and at the runway and a few taxiing aircraft as well. There were also aircraft holding with ZZZ. Normal operations were resumed within 5 to 15 minutes of me taking over. I don't believe without having more CPC's this can be avoided.

Callback: No additional information from reporting Controller.

Second narrative: We had an uneventful flight to ZZZ. We were cleared by approach for the [Runway] XXL visual. Upon checking in with Tower; we were given clearance to land [Runway] XXR. The First Officer queried Tower if they meant [Runway] XXL. The Tower corrected the landing runway to [Runway] XXL. Further into the approach and on short final; we listened to several other transmissions from Tower to other aircraft. Some of these transmissions seemed broken and garbled. We landed [Runway] XXL and cleared the runway to hold short of [Runway] XXR at [taxiway] as instructed. While waiting short of [Runway] XXR it became very apparent the Tower Controller was suffering some type of impairment. At this time of night; all frequencies were combined and the Tower Controller was the only ATC staff radio available at the field. We called Approach Control [and] stated our concern. He advised us he had called the Tower but the Tower Controller seemed irritated with him and hung up on him. Feeling our safest option was to get away from the runways; we requested the runway crossing which was granted. After receiving clearance; we announced our position and intentions as though it was an uncontrolled field. We taxied to the gate and made another call to Approach to let them know the situation was deteriorating. We arrived at the gate safely and by this time; police and paramedics were on the way to the Tower.


Synopsis: Air carrier Captain and Tower Controller reported another Tower Controller became ill will on duty.
Date: 201904
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B737-800
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: Air Carrier
Reporter function: First Officer; 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 Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
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: At FL350 approximately 50 minutes from ZZZ; cabin crew said we had fumes smell in row 12. Deadheading crew in the back confirmed a burning smell with no smoke. Thought it was coming from the entertainment system. Captain asked the Flight Attendant to turn off the entertainment system and see if it went away. Waited a few minutes and said the fumes still [were] there. At this time a passenger moved because she said she felt ill. Diverted to ZZZ1; Captain gave control to me; while he ran [the] checklist. I flew aircraft into terminal area. Once all checklists where complete and the Captain and I formulated complete game plan; the Captain took back control and flew an uneventful visual straight-in to XXR. Taxied clear; looked over by [emergency crew]; taxied to gate.




Synopsis: B737-800 First Officer reported burning fumes in the passenger cabin which resulted in a diversion.
Date: 201505
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Super King Air 350
Operator: Corporate
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Pressurization System
Component problem: Failed
Reporter organization: Corporate
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were leveled off at our cruising altitude FL270 enroute from to ZZZ. A few minutes after leveling off and running the cruise checklist the plane depressurized. The depressurization was rapid; cabin climbing in excess of 3;000 FPM. The first thing I noticed was the pressure in my ear at which point I immediately checked the cabin VSI and the differential pressure gauge. A moment later we got the red altitude light at which point me and the pilot flying both reached for and donned our oxygen masks; ran through the memory items for depressurization and backed that up with the emergency checklist. While running the checklist I requested a lower altitude from Center; an initial vector to [the airport]; and the pilot flying began an emergency descent. After completing the checklist I turned around to check on our 2 passengers and confirmed that they were both putting on their oxygen masks and had their seat belts fastened. center handed us off to another controller who cleared us down to 10;000 feet MSL and asked us if we [had an issue] to which I responded yes. The controller then asked if any services were required; to which I replied no. We leveled off at 10;000 feet and continued the flight without issue and landed [safely].




Synopsis: BE-350 Captain experiences a rapid decompression at FL270 and diverts to the nearest suitable airport.