elihoole/asrs-aviation-reports huggingface dataset:
Date: 201409
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Cockpit Door
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Time Pressure; Workload
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Company Policy; Human Factors
Primary problem: Ambiguous

Narrative: We were originally scheduled to work a flight to CDG. There was a problem with the cockpit door and maintenance was trying to fix it for a long time. The flight attendants were going illegal at XB:15. At around XA:30; crew scheduling decided that we were going to work to LHR and the crew that was supposed to work that flight was going to work to CDG. In order to prevent us from going illegal; scheduling; inflight services and customer services were rushing the swap of crews. Once we got to the London gate; we were rushed to get on and the ZZZ crew to get out; ultimately resulting in the closure of the aircraft door; despite the objection of the flight attendants. Consequently this action by management didn't allow us to complete SOP and FAR requirements as per FAOM. Jumpseat assignments; preflight safety checks; door arming procedures; none of which were completed prior to closing the aircraft door.




Synopsis: An International Flight Attendant reports being rushed to complete an aircraft swap; then having the aircraft door closed prior to the completion of all preflight duties.
Date: 201212
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: ATR 42
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Oil Filler Cap
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Check Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure; Aircraft
Primary problem: Ambiguous

Narrative: Prior to taxi a CCAS ENG 1 OIL warning and local amber OIL PRESS light illuminated and the number 1 engine was shut down in approximately 3-5 seconds. Approximately 40-35 PSI was noted on the oil pressure gauge at shut down. The mechanics were signaled and connected the GPU and the number 2 engine was also shut down. Upon exiting the aircraft the mechanics had a ladder up to the cowling and had it open to the number one engine. It was obvious that an oil leak had occurred and oil was all over the engine and a puddle of oil was under the engine. Operations was notified as well as a log book entry and Maintenance Control was notified. The oil cap on Engine 1 came off due to not being sufficiently secured. There was a log book entry that the oil caps were checked and secured; and it may have appeared to have been secure. This seems to be a recurring problem. Is it only occurring at our company or other ATR operators also? Perhaps ATR or Pratt and Whitney should come out with an AD.




Synopsis: ATR42 Captain experiences low engine oil quantity shortly after engine start and shuts it down. Maintenance finds the oil filler cap off and oil everywhere.
Date: 201506
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Bell Helicopter Textron Undifferentiated or Other Model
Operator: Air Taxi
Operating under: Part 135
Flight phase: Parked
Aircraft component: Fuel Tank
Reporter organization: Air Taxi
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Situational Awareness; Time Pressure
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: 1/4' Drive 7/16' Shallow Socket unaccounted for during FWD Fuel Cell replacement FAA Alert Service Bulletin (ASB) compliance. Socket used to Torque (TQ) Fuel transfer lines inside fuel bladders. Last believed used to TQ Boost Pump and Transfer Pump housing. Discovered missing after Aircraft was fueled for Return to Service. Barrels for waste fuel were full from initial defuel. Aircraft was scheduled for training flights early evening. Thorough search of the facility and aircraft was initiated. Decision was made to enter a discrepancy of missing socket. Entries included inspection of critical areas that would effect safety of flight; ie. Engine Air Intake; Intake Plenum; Engine Deck; Transmission Deck; Flight Control Vertical Tunnel; Flight Controls and Rotating Members. Trash cans that were used throughout duration of ASB compliance were emptied that afternoon. The existing trash cans were sorted through. Given more time; arrangements to empty the waste fuel barrels and defuel the aircraft to inspect Fuel Bladders would have been the next course of action. Training Flight crew was notified of situation and actions taken. Decision was made to accept the aircraft for service. Lack of assertiveness.[Recommendations:]Travel box with tool control. Tool verification at the end of each working day. Trash collection should be done after completion of work.




Synopsis: An Aircraft Maintenance Technician (AMT) reports about the efforts made to locate a 1/4' inch drive; 7/16' inch shallow socket that was unaccounted for after a Forward (FWD) Fuel Cell replacement on a Bell BHT-407 helicopter. Inspections of critical areas that would effect safety of flight were accomplished; socket not found. Fuel tanks were not drained. Training Flight crew accepted aircraft for service.
Date: 201902
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Contributing factors: Company Policy; Procedure
Primary problem: Company Policy

Narrative: While the catering people were changing the aft galley on a 737; I noticed the caterers open the small compartments at 2L. I asked what he was looking for. He said he needed to clean it out and put water bottles here. I reminded him the compartments are not storage areas for the water; these compartments are placard for 10LBS only. They were shoving up to 8 bottles; at 1.5 liters each. I said these items need to go in a carrier or cart; he said no that [company] has instructed them to board the water in this location. On multiple flights on the 737 aircraft; I'm finding 8 to 10 bottles of water each flight; and have to remove them as these compartments are right across from our jumpseat and pose a huge safety hazard. Why is [company] instructing the caterers to blatantly violate the placard weight limit on the compartments; and store galley items in non-approved galley locations?




Synopsis: B737 Flight Attendant reported catering was loading items into locations with weight limitations that were being exceeded.
Date: 202005
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Just after takeoff get a call from cabin there is a strange smell of smoke or odor throughout the cabin. The ovens were not on. In conversation with purser; we were trying to decide about whether we should continue or return. Got another call from cabin and was told that there was another pilot onboard that said that he 'was concerned;' and that passengers were asking. After hearing that key word; made the decision to return to ZZZ. Advised flight attendants and made a PA to passengers. Notified ATC. Accomplished the cabin smoke/fire/fumes checklist. Exceeded 250 kts; to expedite return. Landed XXR and cleared at golf. Inspected exterior by Crash Fire Rescue; and cleared to gate.  When door opened ground personnel could smell strange odor.  Advised that they were considering odor came from electro-static sprayer. One of the flight attendants later said she smelled the same thing yesterday.


Second narrative: After takeoff at about 8000 feet; Flight Attendant (FA) called saying a strange odor in galley. I also smelt what I thought was the galley oven maybe burning. FA informed me that the ovens were all off. We said let us know if the smell dissipates.  Smell was not bad in the flight deck. FA shortly called us back saying the smell is not dissipating and that a deadheading pilot in the cabin is concerned. We then decided to notify ATC followed by the odor/smoke/fumes checklist. Vectored into XXR in ZZZ. Speed was 280 below 10;000 feet. We landed and had CFR and the FAs check for smoke or fire. All clear and taxied to the gate. Maintenance thought perhaps the disinfectant spray was sprayed into vents for too long.


Synopsis: B737 flight crew reported a cabin fumes event during takeoff resulting in a return to the departure airport.
Date: 202102
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Night
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Check Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Multiple Center Hydraulic EICAS messages resulting in a total loss of quantity and pressure in the in the Center Hydraulic System. [Reported situation] with ZZZ Center; complied with QRH procedures; alternately lowered the flaps and landing gear; landed Flaps 20 on ZZZ [Runway] XXC. Towed to gate.Center Hydraulic System failure. Upon landing; Maintenance found a hydraulic leak on right spoiler.




Synopsis: Pilot reported loss of hydraulic fluid resulted in a precautionary emergency landing.
Date: 201407
Local time of day: 0001-0600
Location: ZHU.ARTCC, TX
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class A ZHU
ATC / advisory: Center ZHU
Aircraft component: Autoflight System
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Chart Or Publication; Human Factors; Procedure
Primary problem: Chart Or Publication

Narrative: The MSCOT arrival is not built so the Airbus--as programmed--can fly the arrival without intervention. The FMGC was loaded by us correctly. There was only a slight headwind. The FMGC plans descent to cross JJACK at 19;600 feet which is 600 feet high. The FMGC plans to cross MSCOT at 250 knots; 30 knots slow. These are I assume programmatic errors with the airbus FMGC; but I thought the intent of these arrivals was to simplify [our task] and make our arrivals more efficient. This and several other arrivals into IAH (I have previously referenced the others in an FSAP); do not achieve this. The workload is increased exponentially as designed. These are violations waiting to happen for crews if they are not well ahead of the FMGC's plan. This needs to be corrected; and in my opinion the company needs to issue a communication to aircrews warning of the possible traps on these arrivals. This is not a professional analysis; but the way these new procedures have been instituted is very frustrating. The method puts crews at jeopardy every day. I asked ATC in the past if they were aware of the limitations and they said they had heard nothing. Incredible.




Synopsis: An experienced Air Carrier Captain advised the crossing restrictions of the MSCOT RNAV STAR to IAH appear to be incompatible with the programming/autoflight capability of the A320; planning to cross JJACK 600 feet high and MSCOT 30K slow. Flight crew intervention required to correct those errors significantly increases flight crew workload; draws their attention away from other critical duties and exposes them to certificate action due to non-compliance.
Date: 202004
Local time of day: 1201-1800
Location: ROA.TRACON, VA
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C ROA
ATC / advisory: TRACON ROA
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Distraction
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew FLC Overrode Automation
Contributing factors: Aircraft; Procedure; Airspace Structure
Primary problem: Airspace Structure

Narrative: On a visual approach into ROA runway 24 outside of HIBAN the FAF at 3700 ft the crew received a brief terrain caution that extinguished. The crew had briefed that this may happen and the crew had the hill in sight. [We] continued the approach since we were in daytime VMC conditions.


Second narrative: [Narrative contained no additional information.]


Synopsis: Flight Crew reported a momentary terrain alert while on a visual approach with the terrain and airport in sight and continued their approach.
Date: 202201
Local time of day: 0001-0600
Location: AUS.Airport, TX
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground AUS
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Time Pressure
Second reporter function: Pilot Not Flying; First Officer
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: After clearing the Runway 36L at AUS on Taxiway G; Ground Control issued us taxi instructions:  'G; C; West Ramp on C.  The First Officer then went off frequency to call Operations. Just before reaching taxiway C; I looked to my left in the direction of the upcoming turn and saw a Aircraft Y; moving southbound on C at about 30-40 knots. I had to slam on my brakes in order to avoid a collision. I then made a snarky remark to the Ground Controller that a head's up about Aircraft Y jet would have been appreciated. He apologized and said something to us to indicate that he had been distracted by ramp traffic and airplanes waiting to get to gates. This could have been a catastrophic collision had I not been glancing to my left.  Recommend a dedicated ramp controller that deals with ramp traffic thereby allowing the Ground Controller to monitor and control the movement area.Ground Control distracted with ramp congestion and never told us about other aircraft.Suggest a dedicated Ramp Control frequency and Controller.


Second narrative: After clearing the Runway 36L at AUS on Taxiway G; Ground Control issued us taxi instructions: 'G; C; West Ramp on C. I then went off frequency to call Operations. Just before reaching Taxiway C; the Captain had to slam on the brakes in order to avoid a collision with a fast approaching traffic taxiing on Taxiway C; Aircraft Y. We pointed it out to Ground Control and he apologized. Recommend a dedicated ramp controller that deals with ramp traffic thereby allowing the Ground Controller to monitor and control the movement area.ATC ground controller overloaded with tasks.Get a ramp controller in AUS.


Synopsis: Air carrier flight crew reported abruptly braking to avoid a collision with another aircraft during taxi.
Date: 202011
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Communication Breakdown; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
Contributing factors: Environment - Non Weather Related; Company Policy; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: I am a Ramp Agent in ZZZ.  There is no one to take employees temps as they report to work at the airport. There is currently a sign that reads; take your own temperature and sign your name off. That thermometer has given me reading of 90; 91; 96; etc... Recently; I cannot absolutely confirm; but one of my fellow employees is quarantining with no taste etc...no one that I know of that was working with that employee last week has been notified that they may have been exposed. Why isn't airline following the rules that are so important. We have had fellow employees close family members die of COVID and I along with many others are high risk. It feels like they are not taking this seriously and many of us are concerned and don't want to die.




Synopsis: Ramp Agent reported issues with temperature check procedures at work and the company's lack of communication regarding employees that may have contracted COVID-19.
Date: 201605
Local time of day: 1201-1800
Location: LAX.Airport, CA
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
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: Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant
When detected: Taxi
Result: Flight Crew Returned To Gate; General Physical Injury / Incapacitation
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During pushback; flight attendants advised that a passenger was having a panic attack. Returned to gate and requested law enforcement/medical to arrive at the gate as the passenger quickly disembarked and hurriedly rushed into the terminal before we could complete the parking check.


Second narrative: As we were cleared to push of the gate; we were advised by FA-B there was a passenger that was grabbing his luggage from the overhead bin and wanted to de-plane due to a panic-attack. I immediately told the Captain to stop the push and return to the gate. I advised operations we needed a gate agent ASAP; law enforcement and paramedics to the gate to confirm the passenger's condition. The operations staff responded promptly and the cabin crew opened the door allowing the passenger to deplane. We contacted Dispatch and we closed the cabin door; pushed and the flight continued without further issue.


Synopsis: Air carrier flight crew is advised by a Flight Attendant during push back that a passenger is having a panic attack and wants off the aircraft immediately. The aircraft was tugged back to the gate and the passenger's wishes were granted.
Date: 201402
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: DA20 Undifferentiated
Operator: FBO
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Initial Approach
Airspace: Class E ZZZ1
ATC / advisory: Center ZZZ1; Tower ZZZ
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was with a new instrument student on his first ever IFR cross country; and he was really struggling with a lot of stuff; and as I was helping him set up the approach at night ATC told us to maintain 3;000 until established on the ILS. I was walking my student through setting up for the approach and I looked down at my plates and the Garmin 430 GPS and then I glanced at the altimeter and noticed we were [at] 2;700 FT. As I told him to get his altitude back; ATC kind of yelled at us for being below 3;000 FT and not established on the approach. Then after doing a stop and go the Tower told us we were cleared back to our home airport up to 4;000 and as filed (which was GPS direct). We started flying direct and Tower told us to contact Center. When we went back to that Controller he was upset with us that we weren't flying the published missed; but the Tower Controller never mentioned anything about flying the missed; and had cleared us as filed (which was via direct).




Synopsis: DA20 instrument flight instructor reports an altitude deviation by his student on vectors for an ILS; which is detected by ATC. After a stop and go; the Tower clears the training flight back to home base as filed (direct). This upsets the original Approach Controller who had been expecting the published missed approach initially.