elihoole/asrs-aviation-reports huggingface dataset:
Date: 201604
Local time of day: 0001-0600
Location: ZFW.ARTCC, TX
Flight conditions: VMC
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Flight plan: VFR
Flight phase: Climb
Airspace: Class E ZFW
ATC / advisory: Center ZFW
Second aircraft: MD-83
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Air Traffic Control Separated Traffic; Flight Crew Took Evasive Action; Flight Crew Returned To Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Airspace Structure
Primary problem: Aircraft

Narrative: I was working a moderate arrival push into the DFW metroplex. During the push the [Radar Assist position] advised me of a code 4402 (Aircraft X) in the vicinity of TRL airport climbing out of about 10;000 feet headed south toward the string of arrivals. The code 4402 was climbing toward Aircraft Z out of 16;000 feet. I stopped Aircraft Z at 15;000 feet and called the traffic to him. Aircraft Z never got the aircraft in sight and I descended him once he was clear of the target. The code 4402 appeared to stop at 14;500 feet. I stopped Aircraft Y at 15;000 feet and called the traffic. Then Code 4402 appeared to climb to 15;500. I turned Aircraft Y 15 degrees right to clear the traffic and continued Aircraft Y down to 12;000 feet. After I turned Aircraft Y code 4402 turned to the east into Aircraft Y. I issued Aircraft Y a further right turn to heading 330 and continued to call the traffic. Aircraft Y received a resolution advisory for the traffic and increased his decent rate. At this time I assume the code 4402 saw Aircraft Y and made a hard turn to the south. The new heading put the code 4402 toward Aircraft A; who was descending on the arrival. I was able to stop Aircraft A at 17;000 feet in case the code 4402 climbed from the current altitude of 15;000 feet. Aircraft A saw the code 4402 on his TCAS and eventually got the aircraft in sight. I asked Aircraft A if he could make out the type of aircraft and he replied it was a 'Fast Mover' and 'Dark in color.' I started a track on the code and coordinated with ZHU that the code was headed south toward the IAH arrival route from the NW and advised them to use caution. Approximately 2 hours later Code 4402 flew back through the sector from the south west still at 15;500. The code 4402 performed multiple 360 degree turns and appeared to land at ZZZ airport. I would contact the operators that work out of ZZZ and advise them of the situation and have them use more caution when performing their 'missions.'




Synopsis: An unidentified VFR aircraft was maneuvering in the vicinity of main arrival routes to an airport. ATC had to vector and assign altitudes to several air carrier aircraft to avoid the VFR traffic.
Date: 201202
Local time of day: 0601-1200
Location: PCT.TRACON, VA
Flight conditions: VMC
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E PCT
ATC / advisory: TRACON PCT
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Other / Unknown
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Human Factors; Aircraft; Procedure
Primary problem: Ambiguous

Narrative: We were cleared to descend via the ELDEE 5. Per our procedure we are to set the bottom altitude of the arrival in the altitude window (8;000 FT) when flying in 'VNAV Path Mode.' The aircraft was on target until the Controller issued 2 speed reductions prior to DRUZZ. We asked for and received relief at DRUZZ. The wind at altitude was roughly 280/80. During the second speed reduction the aircraft dropped out of VNAV Path. Simultaneously we had a pack trip off line. The First Officer began the QRH checklist while I continued with the descent; hustling down to at least be close to the crossing altitude at DRUZZ it did not occur to me that there existed a level portion on the descent between DRUZZ and REVUE until it was too late and we descended below 15;000 MSL. Experience with new automation and accepting the lowest form of automation when a problem exists may be the key to preventing such events. Once the aircraft dropped out of VNAV Path I should have immediately selected the next stepdown altitude (15;000 FT) in the altitude window. Being relatively new on the aircraft I am anxious to master its many modes of descent. Choosing the simplest mode when under duress is usually the safest course of action.


Second narrative: However; prior to reaching REVUE we descended through the required 15;000 FT to approximately 14;300 FT.


Synopsis: When their FMC VNAV Path function was unable to comply with both the ELDEE STAR crossing restrictions and ATC speed restrictions the flight crew of a B737NG attempted to manually comply with the crossing at POOCH at 11;000 FT; but while doing so; descended through the required 15;000 FT between DRUZZ and REVUE. Distraction from a tripped pack during the descent was a contributing factor.
Date: 201810
Local time of day: 1801-2400
Location: DFW.Airport, TX
Flight conditions: VMC
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Ground DFW
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon given clearance to taxi [via Foxtrot; we] started taxiing. While on Foxtrot we started to complete taxi checklist. While looking down to verify flaps; replied to checklist then looked up only to see Aircraft Y rapidly crossing my path at intersection Whiskey Kilo. The aircraft did not have [a] taxi light on and was given no clearance to taxi across my taxiway. I applied hard braking to avoid a collision and turned on my Landing lights. ATC queried Aircraft Y with very little reply. ATC was apologetic to us but was confused by what had happened.Event occurred during night operations and at a critical time during the taxi phase. FO (First Officer) was heads down while [I] was in and out during taxi checklist. Aircraft Y approached from left to right (36R-WK exit)/ blacked out except for nav lights and comm out as we taxied on F. We were so close to WK that Aircraft Y was masked behind cockpit window support as we taxied towards 18L. Aircraft Y crossed directly into our path from WK without clearance from Ground. Seemed he was 'zeroed in' on going directly to his ramp with blatant disregard for ATC and other aircraft around him nearly causing a collision.




Synopsis: Air Carrier Captain reported a near-collision during taxi at DFW.
Date: 201605
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Exterior Pax/Crew Door
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Gate Agent / CSR
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors; Company Policy; Procedure
Primary problem: Human Factors

Narrative: Upon arrival at gate; gate agent noticed the exterior handle on the L1 door was not flush with the door and recessed into the soffit of the door. We discussed the situation with both the gate agent and the #1 flight attendant. Apparently there was a recent change to the arrival procedure where the gate agents are now opening the door upon arrival (completing the entire opening procedure) versus the former procedure where the flight attendant would crack the door and agent would open it after it is cracked. I am concerned the gate agents do not understand or have not been trained to ensure the exterior door handle has retracted into the correct position after the door is opened. If they do not check this as they open the door; many 737 aircraft will be flown this way inducing significant airflow forces on the handles which they were never designed to withstand. It would just be a matter of time before a handle fails and falls off the aircraft in flight.




Synopsis: B737-800 pilot reported he is concerned that gate agents may not understand or lack proper training in aircraft door handling procedures.
Date: 201510
Local time of day: 1801-2400
Location: LAN.Airport, MI
Light: Night
Aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors
Primary problem: Ambiguous

Narrative: At night; taxiing from off Runway 10R; we were instructed to take Taxiways J;B; and then A to the ramp.  The signage at the intersection of B and A really should be better.  As we taxied by; I looked over my shoulder and could see that going outbound the signage at that intersection was good. Why is it not so; going inbound?  An aircraft was taxiing out from the cargo ramp and we as a crew really had to stop; go heads inside to check our charts to ensure there was no conflict and that we were really seeing Taxiway A.




Synopsis: Air Carrier Flight Crew reports confusion attempting to transition from Taxiway B west bound to Taxiway A at night due to lack of signage during darkness.
Date: 201603
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Fuselage
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Contributing factors: Human Factors; Incorrect / Not Installed / Unavailable Part
Primary problem: Human Factors

Narrative: I was assigned a structure repair I have never done before and in an area I have never worked. I laid out the repair and asked the crew chief if that looked about right he said yes. I continued on with installing fastener holes using a drill stop until the repair was ready to install. I got clearance to install and installed the doubler. I came into work the next day to find out I had inadvertently drilled into the frame behind the doubler.




Synopsis: On an MD83; when making a structure repair; the repair person inadvertently drilled into the frame behind the doubler.
Date: 201905
Local time of day: 1201-1800
Location: DFW.Airport, TX
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: TRACON D10
Second aircraft: Dassault-Breguet 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)
Anomaly: Conflict NMAC
Detector: Automation Aircraft RA
When detected: In-flight
Result: Flight Crew Took Evasive Action

Narrative: Leveling 10;000 feet on departure; aircraft from behind/below climbed to less than 500 feet of our aircraft and caused climbing RA. We executed climbing RA and advised ATC. ATC gave us climb to 17;000 feet and told Falcon jet to level at 10;000 feet.




Synopsis: Air carrier flight crew had an NMAC with a Falcon jet during departure from DFW airport.
Date: 201509
Local time of day: 1801-2400
Location: SYR.Airport, NY
Flight conditions: VMC
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: We received two flight packages for the evening [for our two planned flight segments].  We noticed on both packages that the NOTAMS seemed to be lacking; specifically for the nightly runway closures that occur in ZZZ.  We knew this due to our experience level at both airports.  I checked the route data brief via the flight ops web page and I confirmed we were missing many NOTAMS that would be applicable for our flights.  The Captain called Dispatch and reviewed the NOTAMS verbally and had them sent via ACARS before we launched.  The Dispatcher told the Captain that they deselect some NOTAMS that they do not find applicable.  I do not agree with this [policy] and did not find this acceptable for our flight. We were specifically missing all the runway and taxiway closure that occur after XA00 at the ZZZ airport. Even if we were scheduled to be in before these closures were to occur; should we block late or have an enroute delay; we would arrive after the closures occurred without the NOTAMS.  Furthermore; if we had some emergency that rendered us without communications and we did not have these published NOTAMS; we could potentially put ourselves and workers on the ground in an extremely dangerous situation because these were omitted from our paperwork.  We only caught this due to our familiarity and experience with these airports.  I do not agree with the NOTAM information being withheld from the aircrew; nor do I think we should have to check behind the Dispatcher via other sources for complete NOTAM information.




Synopsis: A B757-200 First Officer reported they did not receive a complete NOTAM packet for their planned flights and were advised that Dispatchers sometimes withhold NOTAMs they feel are not necessary to include.
Date: 201904
Local time of day: 0001-0600
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Off Duty
Reporter qualification: Flight Attendant Current
Anomaly: Flight Deck / Cabin / Aircraft Event Passenger Misconduct; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Passenger
When detected: In-flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Guest in seat 23F was smoking a cigarette at his seat. 20A came to the back galley and had informed [flight attendants] that there was someone smoking. I immediately went into the main cabin and could smell cigarette smoke. [Flight attendant] and I came across 23F smoking. [Flight attendant] confiscated the cigarette and went to the restroom to extinguish. I told the guest that they cannot smoke on a plane. He informed me that it wasn't his fault and that he did it while he was sleeping. I then confiscated his lighter and told him we will return it when we land and he deplaned. [Flight attendant's] got and presented the disturbance report to the guest.  He was very antsy and would stumble like a zombie to the restroom multiple times before we even performed service. We did not smell any alcohol; I thought maybe he had taken a strong sleeping pill. As the flight went on and after the cigarette incident his behavior became more erratic in being up and about. Even though he had used the restroom at least 15 times he would stumble to the back struggling to find the restroom and door handle. He even would try opening other galley structures. After the incident we as a crew felt it unsafe to leave our doors and had to be vigilant of the guests movements at all times. We had to move the guest seated in 23 A; she felt very uncomfortable and was on edge about the guest. 23 F stumbled and shoved a guest waiting in line for the restroom 9C. I said something to 23F and there was no comprehension of what he did and he just stood there like a zombie. A guest in 29 F was uncomfortable with the guest's behavior and discussed it with me. As a crew we decided for the overall safety of the aircraft to divert to have the guest removed in Chicago. In my personal opinion I believe the guest may have been under the influence of a substance.




Synopsis: Flight Attendant reported a guest smoking and the associated behavior of the guest on the flight.
Date: 202002
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Powerplant Fuel System
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Time Pressure; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Company Policy; Procedure; Logbook Entry; Human Factors
Primary problem: Procedure

Narrative: Aircraft X; ZZZ Line Maintenance; [date]. Midnight shift. #1 eng has running fuel leak from drain mast...; VSV (variable stator vane) actuator r&r which is RII on install and ops/leak check. Lead [Name 1] signed aircraft logbook entry [following day]. No inspector called even though 3 were on duty. RII signed for in aircraft logbook entry by [name 2]. [Name 2] is not an inspector or qualified for RII of any kind. [Name 1] signs airworthiness release for Aircraft X. Aircraft X leaves ZZZ on revenue flight to ZZZ1. Aircraft X returns to ZZZ on revenue flight. (Both flights noncompliant) with false RII sign off in logbook. Midnight shift is notified of failure by both leads and an inspector is called to inspect and do ops/leak check.[Name 3] feels something is not right with this job and starts to ask questions. I return from days off and continue to dig. [6 days later] FAA inspector [Name 4] is notified in the morning. Cause: both leads are inexperienced and lacking in procedures knowledge. Neither has worked in ZZZ as line mechanics. Suggestions: a requirement of 18 months experience as line mechanic should be in place for a crew chief position (leadman) as it is now a mechanic on probation as new hire can bid and get the job. The men he is assigned to lead cannot be trained and steered correctly to succeed by someone barely able to function in this dynamic and dangerous situation.




Synopsis: Technician reported non compliance with Company manuals and procedures caused an aircraft to fly in revenue service twice with falsified log book entries.
Date: 201710
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Sail Plane
Operator: Personal
Flight phase: Takeoff / Launch
Reporter organization: Personal
Reporter function: Vehicle Driver
Human factors: Situational Awareness; Training / Qualification
Anomaly: Conflict Ground Conflict; Less Severe; Ground Incursion Runway
Detector: Person Observer
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was driving my daughter to glider lessons. My car was on the runway. I had my hazard lights on and my headlights on even though it was noon and sunny. I got to an intersection of road and I stopped. I looked both ways. I did see an airplane at one end but it wasn't moving. I waited about 10 seconds. I thought he might be waiting for me but I didn't have a radio to ask so I decided to cross. THAT was wrong. I didn't know better but that isn't an excuse. I thought I was delaying him but I now know that was a terrible decision for me to make. As it turned out the aircraft started approaching. I got out of the way but I scared everyone and feel terrible. In the future I will wait for as long as it takes for the airplane to leave the runway. The airplane has the right of way always.




Synopsis: Vehicle driver reported unknowing entering and stopping a vehicle on the runway while an aircraft was preparing to takeoff.
Date: 202012
Location: ZDV.ARTCC, CO
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZDV
ATC / advisory: Center ZDV
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; No Specific Anomaly Occurred Unwanted Situation
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Human Factors
Primary problem: Chart Or Publication

Narrative: The DEN NIIXX1 arrival [now NIIXX2] has two similar sounding fixes consecutive to each other; BSTON (pronounced 'Boston') and BOSSS; that could be easily confused/misheard.




Synopsis: Air carrier Captain reported similar sounding fixes on the NIIXX 1 [now NIIXX 2] arrival into Denver which might be confused or misheard.