elihoole/asrs-aviation-reports huggingface dataset:
Date: 201508
Local time of day: 1201-1800
Location: MGY.Airport, OH
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class G MGY
ATC / advisory: UNICOM MGY
Second aircraft: Cessna Citation Undifferentiated or Other Model
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: My student and I were about to depart from Runway 2 at MGY. We observed a Mooney land and clear the runway. Once the Mooney was clear [of] the runway on a taxiway my student and I checked the traffic pattern for traffic. Observing no traffic we called on the Unicom that we were departing Runway 2.  As we lined up on the runway I observed a Citation 10 moving toward the runway at the far end of the runway on a perpendicular taxiway. I told my student to stop as the jet turned on the runway and faced toward us. I immediately instructed my student to turn around and clear the runway. Not long after I had turned around the jet departed on the opposite Runway 20. There is no reason that jet could not have taken off with the flow of traffic; I have noticed a recent increase of private jets departing and landing on runways at uncontrolled airports based not on the flow of traffic and/or the prevailing winds but on which runway will expedite their arrivals and departures.




Synopsis: C172 Instructor Pilot reported observing a Citation taking off against the flow of traffic at MGY; a non-Tower airport. Reporter stated he has noticed an increase in this kind of activity from private jets.
Date: 201205
Local time of day: 0001-0600
Location: ZZZ.TRACON, US
Flight conditions: Marginal
Light: Night
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Human factors: Troubleshooting; Training / Qualification; Workload; Communication Breakdown; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Returned To Departure Airport; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon gear retraction; received a L/G Shock Absorber fault followed by L/G doors not closed and L/G not uplocked. I continued to fly the airplane while the Captain worked the ECAM. We were given delay vectors while the Captain tried to establish communications with Dispatch and ATC. The Captain was unable to establish communications on several voice frequencies that he was directed to use by Dispatch. Being unable to communicate by voice. The Captain was forced to use the ACARS unit alone for communication. This greatly impeded our ability to effectively handle the situation and added to the time it took to work the problem. We asked for a hold while we completed the checklist which directed us to 'land at nearest suitable airport.' We made the decision to return to the departure airport but were asked via ACARS to take the airplane to a nearby airport which we declined to do. After completing the checklists and coordinating with Dispatch; Maintenance; flilght attendants and the passengers; control of the airplane was handed off to the Captain and we completed and ILS approach. Landing and taxi in were normal.




Synopsis: An A319 ECAM alerted L/G SHOCK ABSORBER; L/G DOORS NOT CLOSED; and L/G NOT UPLOCKED so the crew complied with the ECAM and returned to the departure airport.
Date: 201407
Local time of day: 0001-0600
Location: HCF.TRACON, HI
Aircraft: Military Transport
Operator: Military
Operating under: Part 91
Flight plan: IFR
Mission: Tactical
Flight phase: Initial Climb
Airspace: Class E HCF
ATC / advisory: TRACON HCF; Tower NGF
Second aircraft: Military
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I had just taken over R3; and the Controller who I relieved apologized for 'what was about to happen.'  I knew immediately; that I'd be writing a report; as soon as I heard that; and I'm correct.  This is RIMPAC.  There are numerous military aircraft all over; and I was given a briefing that NGF Approach would be open 24/7.  This is NEVER the case.  Maybe they are a VFR Tower only 24/7; but they are NEVER an Approach 24/7.  NGF Approach NEEDS TO BE OPEN DURING RIMPAC.  Of course; NGF Approach was closed.  That is a problem all by itself.  NGF Approach needs to be open.  I had four aircraft inbound to NGF; and NGF is only a VFR Tower.  Based on our rules at ATC; we can only allow one-in and one-out of NGF.  An aircraft must report arrival or cancellation before we can clear in another aircraft; or release a different aircraft.  Those are the rules.  That's all we can do.  But; NGF Tower released Aircraft X head on into my Aircraft Y.  They are both IFR.  I do not believe I lost separation.   My D-Side said she did not give NGF Tower permission to release Aircraft X; but NGF Tower released Aircraft X.  Thankfully; a disaster was averted.  Luckily; there was not a mid-air.  There could have been because this was the ultimate worst case scenario.  NGF Tower releasing an IFR aircraft head-on into my arrival on a visual approach.  I asked the supervisor to find out what happened.  This is ridiculous.  NGF Approach NEEDS TO BE OPEN DURING RIMPAC.  I told every aircraft inbound and outbound from NGF that they need to call NGF and complain about this situation.  I told them that when I complain nothing gets accomplished; but maybe if they complained; something would happen.  We need to open NGF Approach.  Please do something.  Please make RIMPAC safer.  Please just do what we were told in the briefing; that NGF Approach will be open 24/7 during RIMPAC.NGF Approach NEEDS TO BE OPEN DURING RIMPAC. Yes; you have my permission to share this and any other report I write.




Synopsis: HCF Approach Controller reports that a Tower departed an aircraft while she had an aircraft inbound to the airport.  This is a one in one out situation and the departing aircraft was not released by the Arrival Controller causing a procedural deviation.
Date: 201902
Flight conditions: VMC
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Turn/Bank Indicator
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: The First Officer/Pilot Monitoring noticed the turn coordinator was unstable and was giving us incorrect indications. After observing erratic indications and taking into consideration the weather that was at our destination; we decided to return to ZZZ. We were VMC and we were halfway to ZZZ1 when the decision to turn back was made. The weather in ZZZ1 was low visibility and so we elected to turn back and remain in VMC. We contacted ATC and got a clearance back to ZZZ. We ended up cancelling a few minutes later. Then; we let [Operations Control] know what the issue and plan was.




Synopsis: C402 Captain reported returning to the departure airport due to a malfunctioning turn coordinator.
Date: 201811
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Hydraulic Lines; Connectors; Fittings
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Release Refused / Aircraft Not Accepted
Contributing factors: Aircraft; Procedure
Primary problem: Procedure

Narrative: Crew entered MRM [Maintenance Requirements Manual] to address a puddle of HYD fluid observed during walk-around that was in front of the left landing gear. The gear well was wet with HYD fluid also. Local techs responded and inspected the aircraft. A [release document] was issued which the pilots were somewhat confused by. The sign off was very contradictory. Technical Support Maintenance Control was called and he said most of the fluid was thought to be de-ice fluid from a de-ice of the aircraft overnight. Biggest problem with this is the aircraft was not de-iced overnight and the puddle was an individual puddle on an otherwise dry ramp. The totality of the circumstances strongly pointed to hydraulic fluid; but de-ice fluid is the easy go-to answer during winter ops. Crews really do know the difference.The sign-off was contradictory from start to finish. It is not HYD fluid on ramp. It is de-ice fluid. However; it is leaking HYD fluid and will be fixed within two days. It is dripping but somehow the HYD fluid goes through a molecular change and falls on the ramp as de-ice fluid. Would be interested to see the MX outcome of this event.




Synopsis: Air carrier pilot conducting preflight inspection noticed hydraulic fluid leak around left main gear. Maintenance was called to inspect and provided a contradictory conclusion that the leaking fluid was de-ice fluid.
Date: 202010
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Second aircraft: Heavy Transport; Low Wing; 4 Turbojet Eng
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Staffing; Airport; Human Factors
Primary problem: Human Factors

Narrative: Takeoff on Runway XXR full length. At around rotation got a push to the right.  Rotated safely and the airplane was climbing normally and no abnormal indications on the ECAM. There was however a heavy aircraft sitting perpendicular waiting to cross Runway XXL. Captain asked if they were cleared to cross that runway because our push to the right seemed to happen around the same time we passed them. Can't really remember what the response was from the Controller.They need to staff the ATC facilities properly. One person handling more than one frequency; or both Ground and Tower. This is not just ZZZ. ZZZ1 is also bad when you add construction to the mix.




Synopsis: Air carrier First Officer reported possible jet blast from a heavy aircraft crossing a parallel runway; while departing.
Date: 202102
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: SR20
Operator: FBO
Operating under: Part 91
Mission: Training
Flight phase: Taxi
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial
Human factors: Situational Awareness; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Regained Aircraft Control; Flight Crew Returned To Gate; General Flight Cancelled / Delayed
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was doing my first solo for my CFI training so I was alone in the aircraft in the right seat. I was performing engine start up procedures and had to lean over to the complete left side of the flight deck to crank the ignition switch. As I was leaned over the engine started and my feet slipped off the brake pedals. The plane moved forward and as soon as I could react I moved the throttle to idle and my feet back to the brakes. I then taxied back into the parking spot; shut down the aircraft; and canceled the flight.




Synopsis: SR20 pilot reported momentary loss of control following engine start from the right seat.
Date: 201908
Local time of day: 1201-1800
Location: SEA.Airport, WA
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B SEA
ATC / advisory: Tower SEA
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Procedure; Airport; Airspace Structure; Chart Or Publication
Primary problem: Airspace Structure

Narrative: On final approach into SEA; we received an RA (Resolution Advisory) from traffic below us in the BFI VFR traffic pattern. Seattle Tower said that they reported the traffic to us but both the Captain and I never heard the call for traffic from Tower. We were established on the localizer and glideslope for the ILS 16R into SEA. The Captain responded to the RA and we continued the approach uneventfully.




Synopsis: Air carrier First Officer reported receiving an RA on final approach for an unidentified VFR target at an adjacent airport.
Date: 202012
Local time of day: 0601-1200
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight; Routine Inspection
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Smell of fumes detected on several occasions including all of last month. Aft smoke detectors go off due to the fumes. Pax (Passengers) complain and makes FAs (Flight Attendants) in the aft sick. We've complained many times and nothing seems to be resolving. Deadhead crew members smell it as well.




Synopsis: B767-300 Flight Attendant reported recurring fume events resulting in passenger complaints and flight attendants experiencing health issues.
Date: 202008
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness; Other / Unknown; Confusion; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Company Policy
Primary problem: Human Factors

Narrative: On this flight; I feel the safety of passengers and crew were put in jeopardy. A uniformed; non-revenue pilot felt that the company policy that all passengers and crew members must wear a face covering didn't apply to him. He stated that he had a doctor's note stating he didn't have to wear it. The agent spoke with him and the working pilot; and they both decided that he didn't need to wear the mask. I didn't feel safe enough to fly; and removed myself from the flight. I question why; in a pandemic; the Captain has sole authority over this type of safety procedure.All employees need to be aware of company safety procedures.




Synopsis: Flight Attendant reported a non-revenue passenger was allowed to ride on the flight and not required to wear a face mask.
Date: 201507
Local time of day: 0601-1200
Location: ZZZ.Airport, 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
Aircraft component: Powerplant Fire/Overheat Warning
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were about 130 NM north of ZZZ at FL370; when the right engine overheat light illuminated. Proceeded with Memory Items and QRH. The light went out when the thrust lever was brought almost back to idle. The right engine was never shut down. After this; we started our decent towards ZZZ. Flight attendants were briefed and passengers were informed about our situation and divert to ZZZ. CFR was requested upon arrival as well. We had an uneventful landing on 18L. Upon exiting the runway we stopped and shut down the right engine. CFR inspected the aircraft; and we were told there were no leaks or other abnormalities. We continued to the gate; where all passengers were deplaned.


Second narrative: Maintenance discovered the overheat/fire detection element touching a duct in the engine bay which apparently caused the false overheat indication. From an aircrew standpoint; there was no means to prevent this event. A learning point to pass along however; would be that the crew must always assume the worst case and take the most conservative course of action to ensure the safety of the aircraft and passengers.


Synopsis: B737-800 flight crew experienced a right engine overheat light at FL370. When the thrust lever was reduced to almost idle the light goes out. The crew elected to divert to the nearest suitable airport and the engine was allowed to continue to run.
Date: 201206
Location: EWR.Airport, NJ
Light: Dawn
Aircraft: A319
Operator: Air Carrier
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Anomaly: Deviation / Discrepancy - Procedural Security; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant; Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: When checking in with the gate agent in the morning in Newark; the agent was late and told us he didn't know how to get into [the computer].  Agent let us in the jetway without checking our ID's!  Our Purser asked if he wasn't going to check; how did he know we weren't terrorists?  He said we didn't look like them.  After telling the First Officer; he made a point of making us all come off with our luggage so he could write our names down.




Synopsis: Air carrier Flight Attendant reported lax security procedures by boarding agent at EWR.
Date: 201707
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Drinkable/Waste Water Syst
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Distraction; Physiological - Other; Workload
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General Physical Injury / Incapacitation
Contributing factors: Aircraft; Company Policy; Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Environment - Non Weather Related

Narrative: Working on the ramp has its own set of hazards. During the upload process hot liquids being poured down the drain which therefore pours onto the gate [where] myself and my coworkers are is becoming an issue. Coffee and or hot water gets poured out and it exits around areas we as rampers must service.




Synopsis: A Ramp Agent discussed the physical hazard's ramp workers encounter when hot liquids are poured into aircraft drains while the aircraft are parked at the gate.