elihoole/asrs-aviation-reports huggingface dataset:
Date: 202006
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Powerplant Fire Extinguishing
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Time Pressure; Training / Qualification; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was performing an Operational Test of the L/H (Left Hand) and R/H (Right Hand) Engine Fuel Shutoff valves. I had armed the L/H and R/H engine fire bottles according to the task and went to ensure that the shutoff valves were closed. After which I had told fellow mechanic [NAME] to return to the cockpit to disarm the fire bottles; reminding him not to press the green switchlights beneath the FIRE PUSH switchlights he was supposed to press. I had prepared to witness the shutoff valves close when I heard the sounds of the engine fire bottles discharging. Mechanic [NAME] had returned to me and I asked him which switch he had hit and he told me he had pressed both of the discharge switch/lights; confirming my suspicions. I returned to the cockpit and verified that the bottles had indeed discharged before pressing both FIRE PUSH switchlights and completing my original task before dealing with the aftermath.I'm not too sure what more could be done to mitigate the issue other than a shield of some sort covering the discharge switch/lights.




Synopsis: Technician reported miscommunication during a functional check of the engine fuel shut off valves; resulting in the inadvertent discharge of both engines' fire bottles.
Date: 201812
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: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel; Person Other Person
When detected: Routine Inspection
Result: General Work Refused
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We have found two more undeclared mail parcels with lithium ion batteries during build up for Aircraft X and also for [another flight]. This is a daily occurrence of finding undeclared dangerous goods in mail. This mail should not be routed to passenger airlines putting passengers and flight at risk for safety. Someone [tried] to mark off the dangerous goods label which is a safety concern as well as trying to make a piece of mail not look to be containing dangerous goods. There [was] no indication that this parcel would be containing lithium batteries.




Synopsis: Cargo Agent reported two USPS undeclared Hazmat shipments assigned to passenger flights.
Date: 201711
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: FCU (Flight Control Unit)
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not 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: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At 35;000 FT; both the First Officer`s and Captain`s navigation displays went blank. The autopilot then disengaged. After about 30 seconds; we got the message single FMC operation. The captain`s navigation display came back on. We were unable to re-engage the autopilot. We attempted to complete the irregular checklist for FMC FAIL. It was determined that the right FMC had failed. The checklist has us go to POS SHIFT (Position Shift) page 3/3. We were unable to do so because both CDU`s were inoperative. We were unable to go to the POS Shift page. At that point; we decided the best course of action was to [return to our departure Airport]. We were still in VHF radio contact with [ATC]. We told them our intentions of returning to [the Airport] and asked for a vector. After turning back; we communicated with the Flight Attendants; passengers; and dispatch. Dispatch agreed that [our elected diversion Airport] was the best place to go. We decided to begin a descent early so that we might burn a little extra fuel so that we wouldn`t land overweight.After about 10 minutes the First Officer`s CDU began to work sporadically. The Captain`s CDU was still inoperative. Using the First Officer`s CDU we were able to program [the new destination]. After about 15 minutes; we were able to engage the left autopilot. The Captain`s CDU began to work during the final 10 minutes of the diversion. We were given vectors to land on runway XXL. It was a normal landing; [which] was under the maximum landing weight.




Synopsis: A Boeing 737 Captain reported that during cruise; both navigation displays went blank and the autopilot disengaged.
Date: 201505
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Reporter qualification: Other Safety Observer
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Ground Personnel; Person Observer
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Company Policy
Primary problem: Company Policy

Narrative: I feel that the new chocking process for mainline flights is exteremly dangerous and could possibly result in a fatality. I am a trained safety observer for my airline. We have made great strides getting our fellow co-workers to follow the now 'old' chocking procedure. From my own personal observations our co-workers are waiting for the all clear signal before approaching the Aircraft under the 'old' way. I feel this 'new' procedure is going to put our co-workers at great risk because after wing walking the Aircraft into the gate their next focus is going to be to get the chocks which are staged in front of the Aircraft. While focusing on getting to the chocks they will be walking past a running engine with the risk of a person being ingested. I think this process needs to left alone and stay with the 'old' procedure.




Synopsis: An airline Safety Observer reports that a new company procedure for chocking arrival aircraft could lead to injury of ramp personnel.
Date: 201306
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb; Takeoff / Launch; Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Aileron Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Ambiguous

Narrative: On takeoff and climbout I noticed aileron feel to be inaccurate; and very heavy. Reviewed logbook further and found this to be a re-occurring issue. Coordinated with Dispatch and made a precautionary landing; to avoid crosswind conditions. Dispatch message said Maintenance would meet our flight. No mechanics met us. Switched aircraft and departed.


Second narrative: No additional information.


Synopsis: B757 flight crew reports very stiff aileron controls during climbout. A Logbook review back more than nine days; reveals the aircraft has a history of aileron write ups. The crew elects to divert to a suitable airport.
Date: 201501
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Government
Reporter function: Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Distraction
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Air Traffic Control
When detected: In-flight; Taxi
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was in the traffic pattern for options; in communication with local 1. When Aircraft X requested to make the next arrival a full stop; with a request for a long rollout; Local Control (LC1) responded in the affirmative. When Aircraft X was abeam the tower on downwind; LC1 cleared Aircraft X for the option. Aircraft X read back the clearance; and then requested to taxi to ramp with LC1; 'In order not to wake up the ground controller.' I want to emphasize at this point; I was not sleeping; or in a sleep-like state. There were 2 people upstairs in the cab; and the LC can confirm that no one was sleeping.LC1 responded; 'I have your request.' when Aircraft X was on the ground; rolling down runway 21L; LC1 instructed the aircraft to exit at taxiway F; contact ground. Aircraft X responded; 'Can we stay with you? We don't want to wake up the ground guy. Oh; never mind; he'll need to get up anyway; he's going to leave the facility in 25 minutes.' This concerns the fact that we close[d soon]. LC1 instructed the aircraft once again to contact ground. When Aircraft X called me; the ground controller; I instructed Aircraft X to taxi to the ramp via taxiway F. Instruct student pilots and instructors that insinuating that someone is asleep in the tower cab; when they are not; is not funny; or acceptable.




Synopsis: Ground Controller reports of a pilot insinuating that Ground Control was sleeping and wanted to stay with Local and taxi to the ramp. Ground Controller was not sleeping and did not think the comments were acceptable.
Date: 201501
Local time of day: 1801-2400
Location: SCEL.Airport, FO
Flight conditions: VMC
Light: Night
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: Tower SCEL
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Human factors: Other / Unknown
Second reporter function: First Officer; Pilot Flying
Anomaly: Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: On departure; the flying crew noted direct illumination from two locations. First was in front; I do not know how far away. I personally saw the second which was off our left approximately 3 miles away. We were climbing through 5;000 feet approximately 5.5 mile off departure end. I estimate the location at PDH/160/6. The flying crew also mentioned three or four other sources; including NW of us once we got turned north. We were flying the DONTI 1C SID.


Second narrative: While departing from SCEL on the DONTI 1C RNAV departure; we experienced 15 or more laser illumination events. This departure departs to the south and makes a big left turn over the city to the north. We were illuminated almost immediately after takeoff (1;000 feet) from a sparsely populated area just south of the airport; which we reported to the tower. Tower acknowledged our report; but didn't ask any questions. The lasers continued as we flew over the city; coming from all directions. Some hit the aircraft and some didn't. I counted up to 5 lasers at the same time coming from different parts of the city. This problem is epidemic and is nearly a national sport!


Synopsis: An aircrew observed 15 or more laser illumination events immediately after takeoff from SCEL (Santiago; Chile).  They reported their observations to the Tower who responded 'Roger'.
Date: 201809
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Aircraft component: Nose Gear
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Vehicle Driver
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Result: General Maintenance Action
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: We were cleared to push Aircraft X. During pushback; the Supertug began to lurch when brakes were applied at the end of the push. The aircraft began to bounce violently in the cradle; with the nose gear nearly escaping the cradle. During that lurching and bouncing; the nose gear rotated approximately thirty degrees while remaining in the cradle. I put the tractor into neutral; brought it to a stop; contacted the Tower to advise of the issue and lowered the aircraft. We chocked the main gear; and I attempted to open the cradle to recapture the aircraft and continue the tow. While opening; the sensor would not read the cradle as fully open; and a hydraulic leak was noticed. [Shop was] notified and removed the tractor with a wrecker for Maintenance. It was returned to service [the day after].The lurching behavior that happened has been previously reported to Management by several [ramp employees]. There has been no fix. If this tractor is not removed from service; an aircraft will escape the cradle and create potential injury or aircraft damage.




Synopsis: Tractor driver reported the tug began to lurch and bounce when the brakes were applied.
Date: 201501
Local time of day: 1201-1800
Location: MMUN.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Human factors: Communication Breakdown; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Ten minutes prior to departure; I tried to get the clearance and could not understand the Controllers' clearance. It was different than the filed route. Another Company flight was blocking my read back thinking it was theirs. I was flying the leg and didn't understand the clearance. The box was loaded wrong for the departure. I was trying to tell the Captain but he was focused on going to get his commuter flight home. He thought we were cleared to six when we were cleared to seven. So; we pushed without knowing the clearance and the box loaded incorrectly to be on time. I challenged the Captain and we got into a fight; which contributed to an unsafe cockpit environment. He acted like he knew what it was all long; which he didn't. He was like we could just figure it out after takeoff.  This led to checklists and procedures to be run in the Red. I don't remember putting the flaps to one. I just read the checklist and didn't back up the Captain to check what I was reading. We taxied out.  He did his throttle burst and didn't get a takeoff configuration light or horn. We ran the Before Takeoff Checklist as we argued all the way out to the runway. He threatened to take me to the Chief Pilot. He acted like he knew what the clearance was and belittled me that I had just a hard time getting the clearance. Then; he explained how we could navigate in the air. I wanted the box correct with a magenta line. We were both in the Red for takeoff and never returned to the Green. I took off and we never had the takeoff configuration go off or the horn. During climb out; I asked for flaps up and realized they were already up. I don't know if he pulled them up without me noticing since I was hand flying. I don't know if we took off with them up or down. I didn't say anything to him or ask him about it. We flew back to ATL in pretty much silence. When we got to ATL; he ran off the plane to make his commute. I tested the takeoff alert and got it in the gate.




Synopsis: B737-700 FO reported the Captain was rushing the flight to make his commute home; making the FO very uncomfortable and leading to a possible zero flap takeoff.
Date: 201811
Local time of day: 1201-1800
Location: PHL.TRACON, PA
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class B PHL
ATC / advisory: TRACON PHL
Reporter organization: Government
Reporter function: Departure; Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X departed PHL assigned a 065 heading. The heading did not separate Aircraft X from the 1;200 FT obstacle (center city) north east of PHL. Aircraft X entered the MVA 2;200 at 900 feet and was not laterally separated from the obstacle. I advised Local East I was turning Aircraft X away from the obstacle and local stated 'He was on a 065 heading.' Headings are routinely assigned without thought for separation required from the obstacle approximately 4 miles NE of PHL. The Tower Controller routinely misinterpret and/or apply the departure heading rules. Tower Controllers should be reminded and retrained on the importance of separating aircraft from aircraft and terrain.




Synopsis: PHL TRACON Controller reported an aircraft was not separated from an obstacle on departure; nor the MVA; which reportedly is a frequent occurrence.
Date: 202009
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Airspace: Class B ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate; In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Company Policy; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: During boarding; flight attendants noticed four passengers that were being loud and disruptive and using foul language. There was discussion on the possibility of some of those in that group being intoxicated. Ground Supervisor was notified and came to address the situation. He elected to remove one of the passengers in that group. The determination was made between the crew to continue with the other Customers in that group.Approximately 30 minutes before arrival in ZZZ1 the in-flight crew called the cockpit to request another Ground Supervisor meet the aircraft due to those remaining three individuals in that group refused to comply with putting their masks over their nose and mouth. Dispatch was not notified at the time due to task loading during the descent and coordinating with Ground Ops and the usual business during the descent/landing phase of flight.  After helping ensure the situation was being resolved upon arrival; I neglected to contact Dispatch.




Synopsis: Air carrier Captain reported a group of passengers appeared to be intoxicated during boarding.  One of the passengers was removed from the flight; the others were reportedly not compliant with face mask policy during the flight.
Date: 202012
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Gate Agent / CSR
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; No Specific Anomaly Occurred Unwanted Situation
Detector: Person Gate Agent / CSR
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Upon coming to work to I witnessed about 30 people all crowded together on the kiosk machines. Social distancing was completely impossible.  ZZZ does not close every other machine; there are 2 rows of kiosks closed for the convenience of bag drop.  There were no stations set up to crowd control.




Synopsis: Customer Service Representative reported crowding and social distancing issues near company provided kiosks in the terminal area.
Date: 201809
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory

Narrative: While level at FL340; we received a TCAS TA; followed by a TCAS RA. The TCAS display showed a target approximately 100 feet above us (+01). We initiated a descent; at which time the RA resolved (went away). We had deviated less than 200 feet from our original altitude (down to approximately 33850 [feet]). We returned to FL340 and reported to ATC. They said they did not show any aircraft in the area.




Synopsis: B757 Captain reported responding to a TCAS resolution advisory at FL340.