elihoole/asrs-aviation-reports huggingface dataset:
Date: 202104
Local time of day: 1201-1800
Location: DFW.Airport, TX
Flight conditions: VMC
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B DFW
ATC / advisory: TRACON D10
Second aircraft: B747 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: We departed Runway 18L in sequence behind a B747. During the climb ATC requested a right turn to 330; then direct BLECO fix. As I began the turn I experienced wake turbulence which caused an uncomanded roll and momentary 'bank angle' aural warning. I corrected the bank and leveled the wings before continuing the turn to BLECO. No other incident occurred after that. Uncommanded roll due to B747 wake turbulence. [We suggest] additional spacing between aircraft would have prevented the roll.

Callback: Reporter emphasized his concern that spacing from heavy aircraft be increased.

Second narrative: A 747 was given an intersection take off clearance on Runway 18L from Taxiway Y or Z; (can't recall). We were given a line up and wait followed by a takeoff clearance from WF (full length). Take off was uneventful. Turning to the north around the fixes BPARK or YAMEL we experienced strong turbulence and a momentary 'bank angle' aural warning. The Captain (Pilot Flying) took immediate corrective action to stabilize the aircraft before continuing the turn to BLECO. We entered the wake turbulence of a Boeing 747 on departure. Increased spacing for Heavy/Jumbo departures and maybe consider alternate departure procedures.


Synopsis: EMB-175 flight crew reported encountering wake turbulence departing DFW in trail of a B747.
Date: 201909
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Other Person
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We received a call from the cabin that we had a Passenger with chest pains. The Captain called ARINC and dealt with communications with STAT-MD; I worked ATC and flew the aircraft. I was preparing to divert when the Captain decided to continue on. STAT-MD at that point asked for us to call them back in 30 minutes. The Nurse Practitioner inserted an IV; and did other procedures. She also said if we run out of IV fluid; then the Passenger would go into cardiac arrest. About fifteen minutes later; the Cabin Crew called again and requested STAT-MD again. The Nurse Practitioner and Doctor onboard wanted to administer more medication. The Flight Attendants were told to prepare to do CPR and to get the AED out. I; again; expected to divert and got ready for a suitable airport nearby. After the conversations between the cabin and STAT-MD; the Captain told me he wanted to continue on to destination; but to expedite. He said STAT-MD said to expedite. I told him this sounded dire and we may want to think about diverting. The Captain said no; he will notify ATC as an emergency and continue on to our destination. I told him I was NOT comfortable identifying as a medical emergency and not treating it as one! If he believed this was a medical emergency; like I did; then we need to treat it as such and get on the ground and get this Passenger help. He ignored me; and there was zero CRM performed. We continued on to destination; and an ambulance met the aircraft and treated the Passenger. After debriefing with the Cabin Crew; it came to my attention that the Nurse Practitioner and the Doctor were angry that we weren't getting on the ground and kept asking the Flight Attendants why we weren't on the ground yet. The Flight Attendants wanted to divert also. Better CRM between Captain and Cabin Crew; and Captain towards First Officer. Better policies for medical situations. Change medical advisory companies; possibly back to [previous medical service provider].




Synopsis: First Officer reported proceeding to destination despite an in flight medical emergency.
Date: 202006
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Flight phase: Parked
Aircraft component: Pitot-Static System
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other Paperwork Audit
Result: General Maintenance Action
Contributing factors: Procedure; Human Factors; Aircraft
Primary problem: Procedure

Narrative: I was told that my manager needed to see me.  My supervisor told me I missed extra verbiage; I needed to add 'Installed Pitot and Static Port were covered' placards to the log page and Maintenance XXX-XX-00 was not enough and showed me where the sign off on the Maintenance task was with.  I thought 'referencing the Maintenance XXX-XX-00 was enough to cover the procedure on the Log page.  Then he told me to go install the placards on the Capt's yoke because of the audit.Installed the 2 placards on the yoke.My manager had my fact finding and told me the same infraction.  I may have been a little distracted trying to figure out how to get all the tags to fit on the circuit breakers for the Pitot and Static port heat.  They were too close together to fit all the tags.  I must of thought I installed them on the yoke after tagging the circuit breaker for the Pitot and Static Heat.I didn't mention it in the Fact Finding.  The announcement of possible involuntary layoffs may happen.  That has been weighing in the back of my mind.  I would be embarrassed if I mentioned that; I know professionally [I'm] not supposed to let that cloud my judgement while doing the job.




Synopsis: Technician reported being distracted by possible lay-offs and did not complete a work order correctly.
Date: 201706
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cardinal 177/177RG
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Training / Qualification
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: When doing a club check-ride and biannual flight review; I lost control of the C177 at the start of the runway.  It went off the runway 10 or so yards up and into the grass; clipping off one of the side marker lights. Some damage was done to the aircraft.




Synopsis: C177 pilot reported a loss of directional control early in the takeoff roll that resulted in a runway excursion.
Date: 201601
Local time of day: 1201-1800
Flight conditions: VMC
Light: Daylight
Aircraft: DA20-C1 Eclipse
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Cruise
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Trainee
Reporter qualification: Flight Crew Student
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Engine failure in flight; landed on highway.




Synopsis: The DA20 lost power in flight so the pilots landed on a highway.
Date: 201908
Light: Night
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: Ramp
Human factors: Other / Unknown; Situational Awareness
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Equipment / Tooling; Human Factors
Primary problem: Human Factors

Narrative: While observing a fuel truck working a RON (Remain Over Night) aircraft at Gate XX; it brought back a memory of an incident that happened when I was a new hire ramp agent [many] years ago. The hose had to stretch a significant distance between the fuel pit and the pump truck. The hose is black and difficult to identify at night; especially on gates that are poorly lit or the hose runs atop pavement instead of concrete. Add the possibility of shadows created by the aircraft or the terminal building limiting visibility - conditions that created exposure to a potential hazard of the fuel hose being run over by a vehicle servicing the aircraft. This scenario happened to me; unfortunately long before we had a [safety reporting] program to offer solutions.




Synopsis: Air Carrier Ramp Agent reported a hazardous situation involving aircraft refueling at night.
Date: 202107
Local time of day: 1801-2400
Flight conditions: VMC
Light: Night
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: Contracted Service
Reporter function: Ramp
Human factors: Situational Awareness; Time Pressure; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter FOD; Ground Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport
Contributing factors: Human Factors; Aircraft; Procedure
Primary problem: Procedure

Narrative: Prior to [the] flight; I was coming off of a previous flight that was on maintenance delay and right after that; lunch. Due to the tight assignment that I was assigned; I was stressed out. This caused me to forget to do my arrival walk around. Once plane arrived; I immediately scanned the offload. After completion of offload I sent two of my agents to run [flight load]. This left me to start the onload with one agent. Once I started the on load; it was weight restricted. I proceeded to load the plane according to the load plan. Upon completing F1 & F2; I started to the aft eventually running out of space; due to restriction. I directed my team to go to the fwd bin; in which I myself moved bags accordingly from F1 to F2. I proved to load the remaining bags in F1. Once I finished the on load I had to call [Manager] due to weight restrictions. I also directed one of my agents to notify the Captain to release the parking brake and let them know that I was contacting [Manager] for weight restriction. After talking to [Manager] for about 5-10 minutes; I immediately got into my push back and proceeded to push the flight out while forgetting to do my walk around.I realized the event occurred; once being notified my Management. The event occurred due to one of my agents placing a vitamin water bottle on the main landing gear upon arrival.The aircraft had to do an emergency landing due to the water bottle being on the main nose gear; which caused the tires not to go in. [Management] notified my crew and I and told us what happened and why it happened. One of the agents admitted that she placed the water bottle upon arrival but forgot that she placed it there.




Synopsis: Ramp Agent reported a precautionary landing due a water bottle hindering the nose landing gear from retracting.
Date: 201203
Local time of day: 1201-1800
Location: ZMA.ARTCC, FL
Aircraft: B737-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class E ZMA
ATC / advisory: Center ZMA
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Communication Breakdown
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Procedure; Staffing; Weather
Primary problem: Procedure

Narrative: R21 is a departure sector receiving aircraft from MIA Approach climbing to 160 heading to the northeast. I was working R21 when; without notification; I begin to get hand offs from Sector 20 for FLL arrivals. The area of weather which closed the FISAL arrival for FLL extended to the southeast and was affecting the departures out of MIA. The departures were deviating to the south of the normal departure route. The departures were head on with the arrivals and all deviating. Sector 20 was unable to descend; slow; and sequence the arrivals before hand offs so they were spinning them entering my sector. The D-Side I had was inadequately trained to be of assistance at the sector. He said he accepted point outs on the aircraft but I am unsure. I requested MIA Approach to spin a departure because I could not climb him and get them around the weather. After the closure of the arrivals the TMU requested 15 miles in trail out the DTAs ZAPPA and VALLY but we were not getting it. The restriction was not being complied with. On a few occasions I turned aircraft without control in order to miss traffic. Finally after 30 minutes of chaos; the departures were ground stopped. It was an unsafe situation! It is unacceptable that TMU is not more proactive to avoid the situations. This scenario occurs almost daily during the summer thunderstorm season in MIA. As soon as an arrival gate closes and the aircraft must be rerouted to a sector working departures; TMU should monitor to ensure the restriction they requested are being complied with. Controllers are often too busy to tell the FLM when the restriction is being adhered to; also timely notification to the FLM from TMU so the FLM can monitor the sector; which in this case did not occur. At the same time; in order to help the high sector provide more spacing to the lower sector; TMU should request in trail spacing from ZJX which should begin immediately. It is not unreasonable to request 5 miles in trail on a certain arrival; instead of the high sector receiving a stack of aircraft all going to the same airport.




Synopsis: ZMA Controller described a chaotic situation when traffic volumes and complexities reached a very high level; the reporter claiming the TMU failed to take necessary actions to temper the complex situation.
Date: 201809
Local time of day: 1201-1800
Location: OAK.Airport, CA
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground OAK
Second aircraft: Widebody Transport
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: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew; Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Upon arriving in Oakland; Ground Control cleared us to Gate XX behind Aircraft Y that was being towed into Gate YY. Upon reaching our J-line; we were marshaled into Gate XX as Aircraft Y was still being pulled into Gate YY. We could see their right wingtip was getting close to us; but our Ground Crew kept marshalling us in. The Captain taxied slowly; and we kept track of Aircraft Y's wingtip. Once parked; we noticed several Airport Operations Personnel; as well as Company Personnel on the ramp taking pictures. Aircraft Y had parked on the wrong line at Gate YY; causing their wing tip to be inside our Safety Zone at Gate XX. After a brief discussion; it was decided that we would need to push back out of the gate to allow Aircraft Y to reposition to the correct line.




Synopsis: Air carrier First Officer reported an aircraft under tow violated their safety zone at the gate.
Date: 201905
Location: ZZZZ.Airport, FO
Weather elements / visibility: Rain
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
ATC / advisory: Tower ZZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was FA #8 at 3L door. Right after takeoff; pungent smell of chemicals came into the cabin like bleach or chlorine. My eyes; mouth and throat [were] immediately affected. Eyes watering and burning; mouth; throat dry with constant taste of bleach; nose burning. I turned to FA #6 at 3R and asked if she smelled it too; and she said she smelled something and came over to my jump seat and said it's way worse on my side. I looked to the FA #2 in the back at 4L and could see she was already on the phone. I walked to the back where I found odor still pretty noxious. FA #7 at 2L smelled it; but to a lesser degree and FA #1 and FA #9 even lesser. Appeared to be mainly on aircrafts' left with concentration at 3 and 4L door areas. This smell lasted probably a good 8-10 minutes; however the affects most of the flight. Both myself the FA #8 and the FA #2 experienced burning irritated eyes throughout the flight along with dry mouth and throat and headache along with burning; dry nasal passage and nasopharynx. FA #1 passed on the info immediately to the flight deck. I was told second hand through FA #1 that it was raining in ZZZZ and the rain hits the runway onto old fuel and chemical spills and that's what we were smelling. Again; this began in the air shortly after takeoff.Suggestions: Fume events need to be taken more seriously for the safety of the crew and passengers.




Synopsis: A330 Flight attendant reported a pungent chemical fume in aft passenger cabin resulting in reported health issues.
Date: 201503
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Approach; Landing
Airspace: Class G ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial
Human factors: Confusion; Distraction; Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Air Traffic Control
When detected: Aircraft In Service At Gate
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Requested ATC Assistance / Clarification; General Police / Security Involved
Contributing factors: Airspace Structure; Procedure; Human Factors
Primary problem: Procedure

Narrative: IFR flight terminated just after midnight. The tower and the approach services were both closed. Center provided GPS approach to RWY 1. I monitored the local frequency until on final approach and then recontacted center with my tail number and requested cancellation of IFR flight in the air. Center responded; and I believed that my IFR flight was cancelled. The landing was normal. One hour later I was contacted by the local police who were sent to find the pilot of a missing aircraft. I called 1-800-wxbrief and they relayed the flight plan closure to center and told me that no additional action was required.In the future; when landing at an untowered (or tower closed) airport; I will make extra effort to communicate an IFR flight plan closure and make sure that I definitely am told that IFR cancellation is received.




Synopsis: A C182 pilot cancelled IFR with ATC prior to landing; but he did not close out his flight plan after landing. ATC requested that local police contact the pilot to verify his well-being.
Date: 201203
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
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: Hydraulic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Human factors: Confusion; Training / Qualification; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew FLC complied w / Automation / Advisory; General Declared Emergency
Contributing factors: Manuals; Aircraft; Procedure
Primary problem: Aircraft

Narrative: Initial problem was left hydraulic pump failure. Secured per QRH and noticed left hydraulic quantity was 1.30. Approximately 10 minutes later we received L HYD SYS Pressure EICAS. Left quantity was rapidly approaching zero. Performed QRH actions; considered options and decided to continue to our filed destination. Informed ATC and declared an emergency. QRH worked well but we found ourselves consulting the Flight Manual for additional info. Questioned the correct checklist as it said: 'Loss of HYD SYS PRESSURE; L only' (probably not verbatim). We wanted to make sure the checklist addressed the loss of the left system and not the left system remaining.




Synopsis: A B757 EICAS alerted left hydraulic pump failure followed later by left hydraulic system pressure at which time hydraulic quantity was approaching zero so an emergency was declared and the QRH followed but the procedure's name confused the crew.