elihoole/asrs-aviation-reports huggingface dataset:
Date: 202004
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Ground Personnel; Person Other Person
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: This cargo section appeared on my desk and I reviewed the [release] noticing the large amount of cargo and nature of the flight. I noticed 3 carts staged of Hazmat [cargo] consisting of 78 pieces at 2;530 lbs. Due to the 15 bag requirement for securing shipment I notified [management] 3.5 hours prior to scheduled departure that the staged loose Hazmat required to be HOFF stating the 15 bags secure rule. The agent stated that the bulk shipment was not Hazmat. I asked for an explanation. I was told by the agent and the ZZZ supervisor that this entire shipment of 56;928 lbs. consisting of 11 PMC pallet boards and the 3 carts of bulk were from the same shipper (who bought the entire aircraft for this charter) and was 1 single AWB. The supervisor stated that there is a 'flaw' in [software] that they had been fighting for a while that with only 1 AWB all the cargo would be considered HAZMAT because it sees it as a single shipment (shipper loaded) I was told that the shipper separated any non-Hazmat into the carts. I advised them to contact the cargo help desk for assistance. After some time and obstacles; the issue was rectified and the shipment was able to stay together and arrive as one to ZZZ1.




Synopsis: Ground personnel reported a discrepancy in HAZMAT cargo in the company load planning software.
Date: 201910
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Turbulence; Windshear; 50
Light: Daylight
Aircraft: Sail Plane
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Approach
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Corporate
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Glider; Flight Crew Flight Instructor
Human factors: Communication Breakdown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Clearance; 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: Returning from local training flight and had entered the ZZZ 'Glider Box' that is used by gliders and tow planes for training and to establish altitude for midfield crossing. All traffic uses the north side patterns. Gliders and tow planes cross mid field from the south.Suddenly we saw a black helicopter rising up through the Glider Box and heading directly at us. The student was on the controls. I grabbed the stick and made a hard turn to the right; but think the student was simultaneously making the same turn. The helicopter flew directly below our right wing as we turned fully to the south. I could see the pilot in the cockpit and it was very loud in the glider when the helicopter passed under. The helicopter made no evasive maneuver. In debriefing with [Company] officials; it was confirmed the helicopter pilot did not see the glider until passing underneath.The helicopter was difficult to see because it was climbing rapidly. I made a radio call regarding the near miss and was given a reply that he had called a take-off that should have made us aware of his presence. Even if we had listened to such a call; there was no way to know his intended direction; high altitude (for a helicopter) or that the flight path would be through the 'Glider Box'.




Synopsis: Sailplane pilot reported that a helicopter departing through a glider designated area resulted in a NMAC.
Date: 202107
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Aeroplane Flight Control
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Weather / Turbulence; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other Landing Roll Out
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Weather; Human Factors
Primary problem: Weather

Narrative: I experienced a ground loop. Wind was 260 at 8kts; and tower had me land on Runway 16. My plane has conventional gear. I got my right wheel down; then the left wheel; then the tail wheel; retracted flaps. Suddenly the plane turned right into the wind; despite my pressing left brake.We ended up in the weeds of the runway safety area; about 50 feet from the runway but facing towards it. I did not drag a wing tip or strike the prop. Neither I nor my passenger suffered any injury. Got grass between the left tire and the rim; and a shallow gouge in the tire's inner sidewall where it took off the brake bleeder valve. No other damage to the aircraft. Could start up; but could not taxi straight. Operations / Fire towed me back to my hangar. I called Tower with a report as requested; and gave a report to the Operations / Fire agent. I suspect I failed to keep the control stick into the wind on roll-out.




Synopsis: Glasair GlaStar 1 pilot reported a ground loop after landing caused by winds.
Date: 201309
Aircraft: B767-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Galley Furnishing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Circuit Breaker (C/B) to meal cart in aft galley popped. Flight deck was notified and I was told to reset the circuit breaker; but if it popped again to leave it alone.  As soon as I reset the circuit breaker; a strong electrical odor started coming from the electrical cord; so I pulled the circuit breaker and notified the flight deck.  They in turn placed the information into the Logbook. I was told the next day; departing ZZZZ; that the power cord to the [meal] cart was replaced. Faulty equipment.




Synopsis: Flight Attendant (F/A) reports a Circuit Breaker (C/B) popped for a meal cart in the aft galley on a B767 aircraft in flight.  C/B was reset on direction from flight deck; but a strong electrical odor came from the power cord to meal cart; Flight Attendant pulled C/B. Maintenance later replaced the electrical cord.
Date: 201911
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not 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 Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: After conducting what I thought was a normal flight; while passengers disembarked; a jumpseating pilot advised us that we had conducted our takeoff without runway lights. If this was the case; it was due to my lack of utilization of the available pilot controlled lighting. Contributing factors include the aircraft lights that illuminated our position on the airport so well that I didn't realize the lack of lighting. Also; the ground was snow covered which; when combined with the ambient light; gave the illusion of a fully lit airport. In fact; while in position on the runway for takeoff; I even advised my FO to 'stay on the centerline' as we didn't have centerline lights!! Also contributing was my unfamiliarity with this airport. I need to have a heightened awareness of conditions at uncontrolled airports and properly get things set up for our operations!


Second narrative: Did not ensure runway lighting was on for departure from ZZZ; [an] uncontrolled airport at the time. Aircraft lighting; cultural lighting and runway markings were illuminating the area for takeoff; but we did not turn on the runway lights. Assess and ensure all available lighting is turned on at uncontrolled airfields to prevent possible issues. Use briefing to catch lighting requirements and discuss the lighting conditions at the airfield.


Synopsis: CRJ-700 flight crew reported departing airport with no operating Control Tower without runway lights.
Date: 202110
Local time of day: 0601-1200
Location: ZZZZ.TRACON, FO
Flight conditions: VMC
Aircraft: Super King Air 300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Aircraft component: Fuel Tank
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Physiological - Other; Time Pressure
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Right aux bladder had been replaced the previous week. Noticed a fuel imbalance during preflight and maintenance said they only had 35 gals in the right aux since they replaced the bladder. We added fuel and left. First landing was uneventful but due to weather; we had just used the fuel in the aux tanks and were just a little bit into the mains tanks. The airplane was fueled and sat for about 1.5 hours while the crew coordinated the next inspection. When crew went to leave; another aircraft was parking on the ramp in front of our airplane while we had the main cabin door open. Crew noticed fuel/exhaust smell in aircraft but attributed it to the exhaust of the other aircraft. Crew started engines and taxied out for takeoff. Several comments were made by the crew members on how bad the smell was inside the aircraft. After takeoff; fuel fumes became more present in the cockpit and cabin. Burning eyes; irritation in throat was experienced by all crew members. Crew elected to go on supplemental Oxygen and return to departure airport for precautionary landing. Crew was getting vectors and believed the smell was getting worse. In order to not have any delays; PIC [requested priority handling] for immediate landing. No further assistance required. Landed without incident. PIC called off [support] trucks when switching to tower.Crew believes there was improper installation of the right fuel bladder causing a fuel leak in the belly of the aircraft.




Synopsis: Air carrier First Officer reported a fume event during initial climb.
Date: 202106
Flight conditions: VMC
Weather elements / visibility: Thunderstorm
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing; Taxi
Aircraft component: Engine Control
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; No Specific Anomaly Occurred Unwanted Situation
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On approach to landing; engines would not idle. Captain was able to slow and stabilize on profile although it required abnormally low throttle setting. Engines would still not idle on taxi in and throttle settings and thrust were not matched.




Synopsis: A319 First Officer reported engine throttle control malfunction.
Date: 201907
Local time of day: 0001-0600
Location: DFW.Airport, TX
Aircraft: A380
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B DFW
ATC / advisory: TRACON D10
Second aircraft: Commercial Fixed Wing
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Procedure
Primary problem: Procedure

Narrative: [A380] was cleared for the visual approach to [Runway] 18R when I was taking a briefing for the position. I heard the previous Controller give a speed of 180 to the marker. The trail aircraft was direct to the second intermediate fix for [Runway] 18R; slowed to 210. Traffic at the time was moderate; but I immediately had to begin slowing the trail aircraft since he was already 8 miles behind. I slowed the aircraft all the way back to 160 knots and gave 10-degrees left to try and make my 7 miles of wake. As I turned on final for the visual approach; I was at 6.98 miles. I tried to give an S-turn to the west; but it was too late; the plane was already in the wake on the inbound turn. I canceled the approach clearance and had him track the localizer inbound at 3;000 feet. As I was trying to get this whole situation figured out; the planes behind were compressing and I didn't have time to let LW1 [Local West 1] know that I was sending the trail aircraft around. LW1 was not pleased.I was instructed to take a position for a short hit toward the end of the arrival push to get my TOP up before my team brief. Arrival Radar did not need to be relieved at that time as the volume was diminishing shortly. I should have watched and let the previous controller work out the situation; but I didn't. I was subsequently relieved after 10 minutes on position; still trying to gather what was going on myself. In my opinion this is a horrible way to safely manage TOP and breaks. Don't page back for 10-20 minute hits during periods of elevated traffic. This places risk into the NAS.




Synopsis: D10 TRACON Controller reported losing minimum wake separation between an A380 and a trailing aircraft on arrival into DFW.
Date: 201410
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Human factors: Communication Breakdown; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Arriving at the gate; the marshaller accepted us and directed us to taxi straight; beyond the lead in line.  He turned away to talk to someone else while directing us toward the aircraft at the next gate over.  Once he realized the aircraft was not where he thought after reestablishing eye contact; he was unable to properly signal a right turn to return us to the line.  His signaling included a pre marshaling alignment signal that was prior SOP; and a handoff signal; which presumably could have been a right turn.  I signaled him to connect headset to the aircraft; and he said he knew how to marshal an aircraft to the right.  I let him know he had put the aircraft in a precarious position and marshaling was required for continued movement; so using an alignment signal wasn't appropriate.  He left the aircraft; and either continued to Marshall our plane into the nearby aircraft; or give the signal to turn over marshaling to the next marshaller.  Eventually; a ramp manager showed up and informed me the aircraft would be towed in.  The actual tow in was not performed in accordance with SOP; and the crew had to be instructed to establish communications with the cockpit.  The crew did not follow any tow in procedure; and disconnected communication prior to completion of tow in; resulting in the aircraft cargo doors being opened prior to brake set.  The marshaller was a lead; as described on his safety vest; but obviously requires retraining of marshaling and tow in procedures.  He placed the aircraft in precarious situations on 2 occasions; and had no ability to correct his actions.  I can't safely be marshalled on my perception of 'what I think he wants.'




Synopsis: A320 Captain reports being confused by a Marshall's taxi directions; resulting in the aircraft being towed into the gate. The Captain believes that the Marshall has not been properly trained to perform the new SOP.
Date: 202003
Location: SJC.Airport, CA
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Human-Machine Interface; Distraction; Fatigue
Second reporter function: Flight Attendant (On Duty)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On day four of day six of flying; tired and distracted I failed to properly disarm the main cabin exit door prior to crosschecking.


Second narrative: On day four of day six of flying; I failed to properly disarm the forward cabin entry door and did not properly cross-check. As I opened the door; I could tell something was wrong; as it felt like it had resistance. I stopped; looked down and saw the casing of the slide was separated from the door approximately 1-2 inches. I immediately told the operations agent to step back and called the Captain. The Captain and myself looked and saw the door was still armed. The Captain called maintenance. Maintenance removed the casing; removed the slide and placed the slide outside. The passengers deplaned safely. I had just finished a 3-day trip prior to this trip. I have not been flying a lot due to my mother being very ill and the passing of my mother-in-law. My mother was just tested for corona virus and thankfully the test just came back negative. She is confined to her room in a nursing home and I am not allowed to see her as of last week. I am allowed to bring her items and drop them off at the front door. The night prior to this trip; I learned that the virus can live on surfaces. I did not sanitize the items I dropped off for her and was concerned I may have exposed her since I just flew a 3-day trip and did not sanitize everything from my trip properly. I picked up both of these trips honestly out of fear of not having trips (earning income) in the future due to possible airline grounding. My mind was very distracted and I was exhausted.This is not an excuse; as I take full responsibility. I am beyond thankful the slide did not deploy. This could have been life altering for the operations officer; my fellow FA's and myself. Cross-checking is imperative; as is staying focused and avoiding any distractions; physical and emotional. Completely focus 100% attention to the cross-check procedure. If this happened 6 months ago; I would say do not fly when exhausted and over-stressed. But unfortunately; due to the corona virus this is not realistic.


Synopsis: B737-800 Flight Attendants reported they failed to properly disarm doors prior to cross checking.
Date: 202006
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Variable winds w/ gusts; 10
Light: Daylight
Aircraft: PA-18/19 Super Cub
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Commercial
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft; Weather; Human Factors
Primary problem: Weather

Narrative: After landing on Runway XX at ZZZ; I was taxiing back to Runway XX for takeoff. During taxi; with winds out of the north and slightly behind me; I had my stick full forward and to the left. Upon approaching a tree line to my right and a row of hangars to my left; a gust of wind pushed the plane's tail to the left; causing the plane to start veering off the taxiway and towards the grass. I put full left rudder in which didn't do anything and so I applied my heel brakes in fear of hitting a taxi-light. With the brakes on and stick forward; the plane tipped forward onto it's nose just off the edge of the taxiway. Throughout the morning into the afternoon; the active runway kept changing at ZZZ as winds kept shifting from the northeast and northwest with gusts; as this is what the windsocks kept showing.




Synopsis: PA18 pilot reported being pushed off the taxiway into the grass by wind gusts and the nose of the aircraft contacted the ground.