elihoole/asrs-aviation-reports huggingface dataset:
Date: 201602
Local time of day: 1201-1800
Location: DEN.Airport, CO
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B DEN
ATC / advisory: TRACON D01
Second aircraft: Small Aircraft
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Flying; First Officer
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude
Detector: Automation Aircraft RA; Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While on a dogleg to final for a visual to 35L in DEN we had a climb RA when descending through 8500 feet to our cleared altitude of 7000 feet. The First Officer (FO) executed the escape maneuver and we notified ATC we were responding to a climbing RA. ATC had previously called VFR traffic climbing to close to our position. TCAS target showed at our 2 o'clock position at a relative altitude of -500 feet and less than a mile when we responded to the RA. Vertical climb required was in excess of 3500 fpm. We climbed to approximately 10000 feet to clear the conflict. We stabilized; queried ATC; and conducted a visual approach to 35L. Jumpseater was the only one of us to acquire the target visually; a [small aircraft]. On the ground I contacted the Approach control supervisor. He stated that there had been a departure from Front Range (TFG) that was supposed to climb to an altitude below the Class B and were investigating. The supervisor later called back and related that the aircraft had violated the Class B by over 800 feet and the resulting proximity of his aircraft to ours was quite close.


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


Synopsis: A320 flight crew reported responding to an RA on a visual approach into DEN when a small aircraft entered Class B airspace without authorization.
Date: 201712
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: TRACON ZZZ
Aircraft component: Pneumatic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After taking off and upon setting climb power; strong engine oil smell in cockpit was detected. Cabin crew also complained about the smell. Feeling light headed and with and eyes itching; we returned to an uneventful precautionary landing. After deplaning it became evident that the entire crew was not feeling well and decided to call paramedics. Crew was transported to local hospital and admitted to the ER for screening and evaluation. Crew was released by ER staff.




Synopsis: A319 Captain reported a strong engine oil smell in the cockpit and cabin during the climb.
Date: 201601
Location: ZZZZ.Airport, FO
Aircraft: McDonnell Douglas Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Dispatch
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Company Policy

Narrative: This flight was operating as a military charter.  The information below is from a shift note I wrote with the intention of sending [a safety report] at later time.XA:44 - sent flight plan for 63.6k.XA:57 - loadmaster calls to advise 102k fuel onboard already.  There was no call to dispatch prior requesting fuel load.Resent flight plan for 100k to account for APU usage.Operating expense went from $21;187 to $22;401; $1;214 increase.XC:44  - crew sent ACARS advising fob is actually 103.6k




Synopsis: Dispatch is not being informed of changes in fuel loads.
Date: 201308
Local time of day: 0601-1200
Location: OSH.Airport, WI
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
ATC / advisory: Ground OSH
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Aircraft
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Before start up there was one Marshal on a scooter to assist in taxi. There were two cones in the taxiway. One cone was moved to the side; but the Marshal said he couldn't move the second one. It was located right of center on the grass taxiway. Before engine start I stated to the Marshal that I will be watching him. After engine start I began to taxi to the left side of the taxiway. I continued to watch the Marshal on the scooter for direction. After passing the second cone I began to move to the right back to the center of the taxiway. That is when I struck the rudder of the Piper parked to my left. I struck his rudder with my left wing. I immediately shut down and with the Marshal and his safety team began exchanging information. I believe that we should have used another taxiway or had a wing walker to assist. I don't believe the Marshal on the scooter was of any help in assisting during taxi. If his duty was not to assist in watching wing clearance he should have stated it. I feel it was a total miss-communication between him and me.




Synopsis: Light aircraft pilot reported he struck another aircraft's rudder with his wing while taxiing.
Date: 202006
Local time of day: 0601-1200
Location: LAS.Airport, NV
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B LAS
ATC / advisory: Tower LAS
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Weather; Human Factors
Primary problem: Weather

Narrative: Final aircraft configuration was just below 1;000 feet AFE. ATC requested 170 KIAS till 5 NM; and Vap was 40 kts less than that. It was about 34 Celsius at the Airport and also contributed to a difficulty slowing down. More awareness about possible limitations slowing an aircraft that was needed to stay fast while dealing with high density altitude.




Synopsis: Air carrier Captain reported not being fully configured for landing before 1;000 feet and cited difficulty slowing down in high density altitude conditions.
Date: 201205
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Ferry / Re-Positioning
Flight phase: Parked
Aircraft component: Airframe
Reporter organization: Contracted Service
Reporter function: Lead Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural FAR
Detector: Person Maintenance
When detected: Routine Inspection
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Procedure; Aircraft; Human Factors
Primary problem: Human Factors

Narrative: During a shift change; a floor beam was picked up on to continue installation. While working the installation it was found that the floor beam had been forced down over a Hi-Lok; causing a gouge in the beam in an area where no limits for damage are allowed; the beam was removed. When we came back to work; the same beam had been re-installed. I feel this is a safety issue. This happened at our Contract Maintenance Repair Station. This was on Air Carrier X's A320 aircraft. Two people were heavily involved with this. It was also brought to the attention of the Director of Maintenance (DOM) with no response.




Synopsis: A Lead Mechanic working for a Contract Maintenance Repair Station reports about a new floor beam that had been gouged when forced down over a Hi-Lok during installation on a Customer A320 aircraft. The beam was removed due to no damage allowed; but later found reinstalled.
Date: 202111
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Gate; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On taxi-out; experienced a smoke/odor/fume event.  Returned to gate. Causal factors unknown.


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


Synopsis: A319 flight crew reported a fumes event of unknown cause during taxi-out and executed a return to gate.
Date: 201902
Light: Night
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Technician
Human factors: Training / Qualification
Second reporter function: Technician
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other In Maintenance
Result: General Maintenance Action
Contributing factors: Manuals; Procedure; Human Factors
Primary problem: Manuals

Narrative: I was asked to be a safety observer for a slide change on door 2L on Aircraft X. I mentioned I had never done the task before; so we went through the slide checklist and removal task card together to check if we had to install anything other than the bottle pin. Upon installing the bottle pin and attempting to show one of the technicians where and how to take the girt bar out. As soon as the handle on the door was touched; it began hissing and almost pulled one of the technicians out of the plane. The door bottle blew the door wide open and the slide deployed.Please make a sign off for the door assist bottle pin to be installed. It is very easily overlooked if being read by an inexperienced person.


Second narrative: Following task card for slide change on L/H #2 door on Aircraft X. I was the technician that was arming and opening the door while my co-worker was going to disarm the girt bar. The door assist bottle started to hiss as soon as I pulled the door handle open. I did not pin the bottle but verified the pin was in.Clear instruction on how to pin and disarm the door assist bottle for Airbus aircraft task card like the Boeing aircraft slide work instruction.


Synopsis: Maintenance personnel reported inadvertently activating the aircraft cabin door slide while working on it.
Date: 202107
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Other Departure / Pushback
ATC / advisory: Ramp ZZZ
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Vehicle; Ground Event / Encounter Ground Equipment Issue
Detector: Person Ground Personnel
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On Gate X at XA:56; Vehicle drove and stopped behind the aircraft while mid push. The vehicle was a full gate length away at the start of the push. Wing walkers were in position to stop the aircraft and were clearly visible to all traffic. No damage occurred and the push was completed after the vehicle was moved out of the gate.




Synopsis: Ground employee reported a vehicle stopped behind an aircraft being pushed back for departure; requiring the push back crew to stop operations.
Date: 201811
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Dispatch
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: During departure from ZZZ everything was normal at the gate other than running slightly behind schedule. The Gate Agent was very busy with boarding passengers and other duties. After a normal taxi; takeoff; and climbout; we received an ACARS message from Dispatch while passing through FL 260. The messages stated the following: 'you have slides in your forward cargo bin. The weight was accounted for correctly; however; the Gate Agent forget to give you the HAZMAT paperwork.' I am paraphrasing; that was the basic message. We felt safe to continue to destination without further issues. Mistakes happen. My only suggestion would be if possible; when HAZMAT is on the aircraft; include that in the remarks section of the [Weight and Balance]; that would be another possible way to catch missing paperwork.




Synopsis: B737-700 Captain reported receiving notification during climbout that HAZMAT flight documents were not included on flight crew release.
Date: 201810
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Ramp
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
Result: General None Reported / Taken
Contributing factors: Airport; Company Policy; Procedure
Primary problem: Airport

Narrative: I was dispatched to move Aircraft X to spot 12 on the east hangar. Spot 12 as well as most spots at the east hangar are not marked for [this size / type of aircraft] and every day we are asked to move these aircraft to pads /spots that are not marked for them. Parking aircrafts on pads/spots that are not marked for the type of air craft getting parked there can cause damage to the aircraft; ground equipment; vehicles; and cause injury to employees. When parking these aircraft on these unmarked spots; marshaling in the super tugs you have to guess and estimate when and where to stop the aircraft so that aircraft and wingtips are in the operational safety zone and are not hanging over to hit ground equipment; mobile stairs; or vehicles. Also the OSZ (Operational Safety Zone) painted lines are very dull and faded and very hard to see at night with very limited lighting that we have over at the east hangar. Spot 12 always is a very tight fit next to a building and when parking [this size / type of aircraft] you have to pull up really close so that the ground power cord can reach but also its really hard to move the super tug out and we've had super tugs get damaged already when trying to put tug off aircraft off at this spot. I have brought this us to my supervisors' as well as well as my manager's attention and the response I got was that 'it's temporary for the east hangar and all the holding/ parking spots for aircraft will be under construction very soon.' I feel a lot can happen in a temporary situation; with damage to aircraft; ground equipment; vehicles; and/or injury to employees and as far as I know of constructions is months away.




Synopsis: Ramp Agent reported being asked to move aircraft to airport pads/spots that are not marked causing conflict with ground equipment.
Date: 201903
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Pre-flight
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Accessible Dangerous Goods package was loaded incorrectly. First officer was unable to see the label. Ramp personnel quickly remedied the issue.Cause: Lack of attention to detail.




Synopsis: B767-300 Captain reported hazmat was incorrectly loaded; ramp personnel corrected the error.
Date: 201908
Local time of day: 0001-0600
Light: Night
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Situational Awareness
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Dispatch
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: There are fundamental flaws with the [Flight Plan Manager] system being used for US method of dispatch.  We have many situations where the software takes liberty changing paperwork/inputs without Dispatcher being made aware of them. For example after a Dispatcher creates a release by pressing the release button it is not sent to stations until after the [Load Report] is generated by AERODATA.  In the meantime the Dispatcher could leave the flight to look at other things.  However this releases the Dispatcher lock on the flight plan and the system will take liberty in changing parameters of the flight plan. If the Dispatcher were to return to the flight and not catch that there were changes made the Dispatcher could submit Release 1 with changes they were not aware of to the station to print. The system should not be able to make changes to the release after the Dispatcher has pressed release and creating a version of the flight plan. However whether that was the case in this this instance is probably not likely. However terrain page didn't even match the points presented in the remainder of the release [Flight Plan] legs page. The system creating paperwork that doesn't agree with itself is not OK and indicates a lack of robust programming and verification of data. Either way the system should be hardened and known vectors for the generation of incorrect paperwork locked down.




Synopsis: Air carrier Dispatcher reported operational issues could arise as a result of software anomalies.
Date: 201907
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: General Flight Cancelled / Delayed
Contributing factors: Company Policy; Procedure
Primary problem: Company Policy

Narrative: I was the Captain on the flight operating [from ZZZ.] ZZZ had just experienced thunderstorms and when we taxied out for departure we saw that the ground delay for takeoff was going to be extensive. We were in a large line creeping along towards the departure runway. When we approached the 90 minute point from our out time I asked the flight attendants if they could walk through the aisle with water and pass out the delay snack without using the serving carts. We were moving ever so slowly and I felt it was safe for them to perform this duty. As stated in the Company Manual the DOT Tarmac Delay regulations states that passengers must be provided food and water no later than two hours after actual gate departure. Because we were at the 90 minute point and I had no firm idea if we would be airborne by the two hour point; I asked the flight attendants to perform this service. The DOT Tarmac Delay regulations is very clear that Non-compliance may result in fines to the airline of up to $27;500 per passenger. We need more guidance on how to handle this situation. Do we violate the two hour rule to provide food and water if we are inching along on a taxiway? Do we ask ATC for a place to park to provide food and water so we don't exceed the two hour requirement but risk losing our takeoff time and now may have to return to the gate?




Synopsis: B737 Captain reported concerns over complying with DOT Tarmac Delay regulations and Company Manuals.