elihoole/asrs-aviation-reports huggingface dataset:
Date: 201706
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Security; Deviation / Discrepancy - Procedural Hazardous Material Violation; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General Physical Injury / Incapacitation
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: I was working in the bag room; taking bags out of the lateral; when a bad smell came out of one of the bags. It made me nauseous instantly; my mouth got watery and salty; I went to the bathroom [and] I felt like I was about to throw up. Supervisor was in the bathroom; asked me if I was ok; I said no and explained what happened. I was still feeling sick [so] I went to the sink to put water on my face when my feet got real itchy. I took my shoes off [and] scratched my feet when they started to swell. All of a sudden my whole body started itching. I looked in the mirror my face and ears were also swollen; a rash on my back; neck; and stomach appeared. I went to the supervisor's office showed her what was happening; she called to have someone take me to [a medical facility]. I was getting worse [so] she decided to take me herself. We walked to the elevator [and] that's when I felt like I was about to pass out; so she walked me back into the break room where I started to feel like I couldn't catch my breath. 911 was called. Paramedics couldn't get a blood pressure or pulse. I was taken to the ER where I was treated. I feel some of this bags need to be wrapped in plastic or some kind of wrapping to avoid the dust and the liquids that come through and/or flies of these international bags.




Synopsis: Air carrier baggage handler reported experiencing nausea and other physical issues presumably related to fumes from one of the bags that came off an international flight.
Date: 201207
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Fuel System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying

Narrative: Pushback and engine start were normal. Ground Operations did not report any issues when I cleared them off headset. [We] taxied to Runway 22L for departure. After receiving and complying with a lineup and wait clearance; Tower advised us that a city operations vehicle had observed us trailing some type of fluid during taxi. They did not know the source or type of fluid. All cockpit indications of fluid quantity and pressure were normal. We coordinated with Tower to have the city operations vehicle drive around the aircraft to try to determine the source of the leak while we remained in position on the runway. After driving around the aircraft; the city operations employee pointed at the # 2 engine; and through hand signals; indicated that there was a significant leak from that engine. I told the First Officer to ask for a clearance to return to the gate and I secured the # 2 engine. We returned to the gate on one engine; and as we joined the parallel taxiway to return; we noticed a significant trail of fluid from our taxi out that I would estimate was around one foot wide. As we approached the gate; I noticed a puddle of fluid where we had held during engine start and tow bar disconnect. The puddle was approximately 50 feet in diameter. We deplaned all passengers for an engine run that was coordinated with Maintenance. After the engine run was completed; the aircraft was taken out of service for a significant fuel leak at idle.


Second narrative: [Narrative #2 contained no additional information.]


Synopsis: After taxiing into position for takeoff; B737-700 flight crew was informed by a ground vehicle of fluid leaking from the Number Two engine. Upon return to gate; a significant fuel leak is discovered.
Date: 201901
Local time of day: 1201-1800
Location: MSLP.Airport, FO
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
ATC / advisory: TRACON MSLP
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: Workload; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew FLC Overrode Automation
Contributing factors: Airspace Structure; Procedure; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: Flight ZZZ-MSLP. We had a late runway change and STAR assignment that resulted in being high at D 5.0 YSV on the arrival. The cause of this was the inability to modify the arrival and execute the STAR in FMC. We reverted to heading select and level change to comply with the arrival. We notified ATC of our issue and was cleared the visual approach before intercepting ILS 07 Approach. It was a stable approach but the STAR altitudes and intercept altitude from MORAM 1K STAR to ILS 07 do not allow FMC to execute the modified route. While reviewing the 737 Flight Manual I found what Boeing has said it 'has advised incidents' concerning these issues. It's described on FM 4.30.10 Problem is in reviewing the STAR and ILS I do believe this 'sets up pilots' to not be able to successfully and safely fly the approach and arrival. [Report] will be filed and [Union Rep] will be notified. I believe a NOTAM or 10-7 note reflecting this should be addressed as this is time critical.




Synopsis: B737 Captain reported the STAR altitudes and intercept altitude from MORAM STAR to ILS 07; does not allow FMC to successfully and safely execute the modified route.
Date: 201606
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Light: Daylight
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Second reporter function: Captain
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Process of push back and engine start; after engines were noted stable; Captain called for taxi and released the brakes and the aircraft began to roll as he ask the First Officer (FO) did you see a wave off on your side? (FO) immediately commanded STOP; STOP; and applied the brakes stopping the aircraft because of tug and personnel were still present under the aircraft and tug visible under the FO window. Tug then began to pull away and push back crew came out from under the aircraft and administered the wave off with no indication of injury or equipment damage.


Second narrative: [Report narrative contained no additional information.]


Synopsis: Air carrier flight crew reported a breakdown in communications with the ground pushback crew during the disconnect phase.
Date: 201911
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Daylight
Aircraft: EMB-505 / Phenom 300
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Corporate
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Confusion; Workload; Distraction; Situational Awareness
Anomaly: Deviation - Speed All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: Departed Runway XX at ZZZ using the company noise abatement procedure. Early in the climbout icing conditions were encountered and there was some confusion and concern on my part as Pilot Flying about the speed at which we should have been climbing. The noise abatement procedure calls for V2+20 KIAS with partial flaps (Flaps 1); however there is minimum speed with airframe anti-ice on of 150 KIAS with flaps up. I was unsure about whether to climb at V2+20 (in this case 135 KIAS) or if I should discontinue the noise abatement procedure and accelerate to a speed at or above 150 KIAS. I was on IOE and initiated a discussion with the instructor; who was Pilot Monitoring on this leg; regarding my uncertainty about the speed. During the course of our discussion; while on an assigned heading; ATC issued a clearance to proceed direct ZZZ1 VOR out of 11;000. I can't recall the altitude at the time the clearance was issued; but believe it to have been approximately 9;000 and very shortly after the handoff from Approach to Center. Passing through 12;800 feet; ATC reissued the clearance to proceed direct ZZZ1 VOR and we immediately complied. The flight continued safely to the destination without any further issues.Although a decision needed to be made about the climb speed and some crew communication was necessary; the error might have been avoided had some of the discussion been postponed until later in the climb.




Synopsis: EMB-505 flight crew reported deviated from clearance during departure.
Date: 202108
Local time of day: 1801-2400
Location: ZZZZ.ARTCC, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B747 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Cruise
ATC / advisory: TRACON ZZZZ
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; Flight Crew Diverted; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Company Policy
Primary problem: Aircraft

Narrative: Suspected  #4 Hydraulic Leak Divert to ZZZZ1Departed ZZZ enroute to ZZZZ. Several hours enroute we noticed #4 hydraulic system indicated abnormally low quantity at approximately .45.We continued to monitor and noticed a .01 decrease per approx every 30 to 45 minutes. Over [geographic area 1] as we neared [geographic area 2] we became concerned that we did indeed have a slow hydraulic leak as we were now indicating .39.We preempted the 'hyd quantity low 4' QRH procedure in hopes that depressurizing system 4 pumps would slow or prevent our suspected leak given we still had nearly 6 hours to destination. If the current trend continued we would have faced a possible loss of system 4 resulting in degraded flight controls and manual gear extension at destination.After depressurizing system 4 the downward trend in hydraulic quantity continued. Shortly after our coast out point of ZZZZZ I made the decision to advise company operations and ATC of our situation and made arrangements for us to divert to our planned enroute alternate of ZZZZ1.We repressurized system 4 prior to landing as per the QRH and landed without further incident at ZZZZ1.Plan more ground time to address trending maintenance items on a more regular schedule to strike a balance with the demanding flight schedule as hydraulic issues are appearing more regularly and have been documented in recent logbook discrepancies with this particular aircraft.




Synopsis: Captain reported diverting due to #4 hydraulic system losing quantity.
Date: 201710
Local time of day: 1201-1800
Location: LGA.Airport, NY
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B NYC
ATC / advisory: TRACON N90
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Human Factors
Primary problem: Ambiguous

Narrative: We were hearing drone reports by ATC. We were eventually given a traffic advisory for the drones ourselves. We kept a look out and the First Officer spotted 2 drones flying about a half mile laterally to the right of us; and 500-1000 feet below us when we were 2 miles prior to GREKO on the approach for Runway 22 in La Guardia. He kept them in sight and we were clear of them; continuing without having to take evasive action. The sun was setting and he wasn't sure if the light was reflecting off of red paint; or if the drones were emitting a red light on each of them. We reported the drones to ATC and made a phone call to them after we parked at the gate.




Synopsis: Air carrier Captain reported sighting 2 UAVs while conducting an approach at LGA. The event was reported to ATC; however no evasive action was taken.
Date: 202109
Local time of day: 1801-2400
Location: LIT.Airport, AR
Flight conditions: VMC
Weather elements / visibility: 10
Light: Dusk
Aircraft: Small UAS (At or above 0.55 lbs and less than 55 lbs)
Operator: Recreational / Hobbyist (UAS)
Operating under: Recreational Operations / Section 44809 (UAS)
Flight plan: None
Mission: Recreational / Hobbyist (UAS)
Flight phase: Descent
Airspace: Class G LIT
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Reporter organization: Recreational / Hobbyist (UAS)
Reporter function: Person Manipulating Controls (UAS); Remote PIC (UAS)
Reporter qualification: Other TRUST completion certificate
Human factors: Training / Qualification; Situational Awareness
Anomaly: Conflict NMAC
Detector: Person UAS Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was flying my small UAS when what was possibly a trainer aircraft flew over so low that I didn't see the aircraft until it flew over. The aircraft was so low that my drone was warning me about being too close to the aircraft as I was descending to land. I was running navigation lights as required by regulations that can be seen for 3 miles. The aircraft seemed to be around 300 to 400 feet above ground level and I was about 190 feet above ground. I am flying in class G airspace with woods all around me. My drone was kept in visual line of sight the whole time and was fully legal.

Callback: Reporter stated the aircraft was a low wing trainer; type unknown.



Synopsis: Hobby UAS pilot had a near miss with a general aviation aircraft in uncontrolled airspace.
Date: 201311
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight phase: Cruise
ATC / advisory: Center ZZZZ
Aircraft component: Fire/Overheat Warning
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Diverted; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At cruise 45 minutes into flight had a status message of 'overheat Circuit R 1 and Fire Loop 1 Eng R'. Sent Maintenance a message and continued. 2+30 into flight got EICAS message 'Det Fire Eng R'. Consulted with Maintenance and Operations and determined we had no fire detection on right engine. [We were] concerned due to time lapse between status message and EICAS message. [We] still had 4+30 enroute over sparsely populated area with few airports to divert to. Consulted with Duty Officer and determined safest course of action to divert to [a nearby airport] rather to continue with no fire detection on right engine. Upon landing stopped on taxiway and had fire and rescue inspect right engine after we shut it down to confirm no fire indication prior to entering ramp. [We] advised ATC reason to divert due to maintenance precaution.




Synopsis: B777 First Officer reported losing fire detection on right engine 2 1/2 hours into a long international flight. They elected to declare an emergency and divert to a nearby airport.
Date: 201311
Local time of day: 1201-1800
Location: CLT.Airport, NC
Flight conditions: VMC
Light: Daylight
Aircraft: Super King Air 350
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground CLT
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Private; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: CLT Ground instructed us to taxi to Runway 36C; via 'D'; left on 'R'; hold short Runway 36R at 'R'. After stopping at the hold short line for Runway 36R; Ground Control instructed us to 'Without Delay' cross Runway 36R. A quick check to the left; the power was brought up 'Without Delay' to cross Runway 36R as instructed. As we proceeded the Pilot Flying slammed on the brakes; as he took another look left to see a B737 landing on Runway 36R; crossing right in front of us. After the B737 had passed CLT Ground instructed us to stop; which we had already done. Assessing the dangerous situation we were now in on the edge of [Runway] 36R; we felt for safety we needed to exit the runway before another aircraft landed. As this decision was made; CLT Ground instructed us to continue across [Runway] 36R and join 'A' on the other side. We continued with the crossing and proceeded to [Runway] 36C with no other problems. Since we complied with every instruction during this chain of events; in no way did we violate any FARS. Since I do not have the recording attached; once we were cleared to cross Runway 36 'without delay' it took 7 seconds for the Ground Controller to try and stop us. As we were waiting to take off we were told to call Tower. Upon arriving at our next destination; I spoke with the CLT Tower [Controller] and he stated that 'upon review of the tapes and interview with Controller; we in fact did nothing wrong and complied with the Controller's instructions'. As a result of this issue; I would suggest that all GA aircraft arrive and depart Runway 36R/18L which would greatly enhance safety. Thank you for your attention to this matter.




Synopsis: BE-350 Captain reported he was cleared to cross CLT Runway 36R but as he entered the runway he saw a landing aircraft cross their path so he quickly stopped the aircraft.
Date: 201403
Local time of day: 0601-1200
Flight conditions: VMC
Light: Daylight
Aircraft: Bonanza 36
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise; Takeoff / Launch
Airspace: Class E ZZZ
Aircraft component: Fuel Selector
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: I was forced to land in a farm field due to an engine failure. I had my airplane inspected by two mechanics who returned the airplane to service or confirmed the engine failure would not recur. The issue or purpose of this report. I departed after balancing the fuel between my tanks but ultimately departed with my right tank showing 15-20 gallons; my left tank however may not have been above the arc or 13 gallons that is required. I am uncertain as to the exact amount because my flight was three minutes long and I had no intention of changing tanks. I also don't know if this type of situation warrants a notification...but; felt it was probably appropriate to report. It should be noted; the flight occurred without incident.




Synopsis: A36 pilot experienced engine failure and landed in a farm field. After a maintenance inspection and fuel balancing the aircraft was flown a short distance without the minimum required fuel in the left tank.
Date: 201812
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: PA-28R Cherokee Arrow All Series
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Landing Gear
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Ground Event / Encounter Gear Up Landing
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Missed required documents (Registration/Airworthiness Certificate) on preflight. In pattern to land; pilot moved gear handle to extend gear. All indications normal. Upon touchdown; plane skidded on belly. I don't know what happened to cause [the] malfunction.




Synopsis: PA-28 pilot reported gear-up landing following normal indications prior to touchdown.