elihoole/asrs-aviation-reports huggingface dataset:
Date: 201507
Local time of day: 1801-2400
Location: BWI.Airport, MD
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground BWI
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Communication Breakdown; Confusion
Second reporter function: Captain
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: We were cleared to push back from the gate at BWI 'at your discretion; caution for aircraft pushing from [nearby gate;] expect Runway 28.' The Captain relayed these instructions to the pushback crew and the pushback crew decided to push us to our left; tail west; away from [the other aircraft.] The aircraft was pushing into the alley.During our push; Ground told us to push back far enough to allow another taxiing aircraft to pass from our right. We did and continued to push deep tail west onto [the taxiway.] As the pushback crew was disconnecting; Ground Control commented to us that they had recently noticed a lot of pushes onto the (movement area) and that a clearance to push 'at your discretion' meant to push into the alley (non-movement area) not onto taxiway.The Ground Controller specifically stated she realized we do not have much control over how our pushback crew pushes us and that BWI Ground Control had been seeing several similar types of pushes into the movement area like this. She asked that we relay this problem to our ramp personnel and to not do this in the future.


Second narrative: We were given permission to push from gate; without any special instructions. The tug driver pushed us onto the taxiway to our left. After doing so; the Ground Controller mentioned that the clearance meant that we were to push into the alleyway and not onto [the taxiway]; and that they had been seeing that happen a lot. The Jeppesen 10-7 page only mentions that pushes from the gate should just not block the taxiway.


Synopsis: Air carrier flight crew reported being told to push back at their discretion. Crew pushed aircraft on to active taxiway. After calling ready ATC advised crew they should have pushed into the alley; not on the taxiway.
Date: 201906
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Ground Personnel
When detected: Taxi
Result: Flight Crew Returned To Gate; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Hazmat loaded without secure and aircraft returned to gate to move 421 lbs. of mail to other pit to add 15 bags with the Hazmat.




Synopsis: Ground personnel reported aircraft ground return to correct Hazmat cargo configuration loading discrepancy.
Date: 201910
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Dawn
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: No Specific Anomaly Occurred All Types
Result: General None Reported / Taken
Contributing factors: Equipment / Tooling; Company Policy
Primary problem: Equipment / Tooling

Narrative: Printed copies of the weight and balance information and preflight performance data made Captain's review of data more clear and precise; enhancing safety. Captain had been off for six weeks; moving slowly through checklists and flows. The improvement in my situational awareness between this particular flight (having the printout) and the others during the same trip was significant; highlighting items on the report and completing an overall review (with all data presented on a single page) allowed me to create a better shared mental model with First Officer. On subsequent flights; returning to paging through FMC screens to review data and conduct checklist; it felt as if crew had returned to a program of haphazard; degraded; antiquated and less precise operations.Recommend installing flight deck printers on all Company aircraft.




Synopsis: B737-800 Captain reported that the addition of a cockpit printer resulted in greatly improved situational awareness.
Date: 201702
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Citation II/SP (C551)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Oil Filler Cap
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Private
Human factors: Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic; Flight Crew Inflight Shutdown; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Departed on IFR flight. Climbing through 16;000 ft MSL; low oil pressure annunciator on left engine came on. Pressure tape started dropping. I immediately started a 180 turn back; notified ATC; but did not declare an emergency. ATC gave me vectors after I already turned back. As I joined the vector route; I came within 4.9 miles of another aircraft who was #1 for landing; I was #2. If I would have declared emergency; ATC would have cleared me #1 for landing. I secured the left engine and proceeded with a single engine approach and landing. Cause of loss of oil pressure was a dipstick that popped off during flight. I added oil and proceeded to depart. Before departing; I called Center at their request.Single pilot; there was a lot to do. Aviate first; communicate second. Still; I should have declared an emergency when requesting return. However; left engine oil pressure tape was still in green. When it dropped to red I should have advised ATC and declared.




Synopsis: CE551 pilot reported low oil pressure on an engine during climbout and elected to return to the departure airport prior to obtaining ATC clearance.
Date: 201808
Local time of day: 1201-1800
Location: ZJX.ARTCC, FL
Flight conditions: IMC
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
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: Communication Breakdown; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: While climbing out of TPA we encountered a significant lightning/static discharge event while flying through an outflow area significantly downwind of an area of dissipating thunderstorms. The flight conditions consisted of a smooth ride; light rain and intermittent stratiform clouds. Our Multiscan radar showed us in an extensive area of precipitation depicted in green. The nearest contour (in yellow) was over 80 miles away. I don't recall anything we did contrary to the FM weather policy. The airplane remained out of service for over 24 hours and had 17 defects detected in the maintenance inspection. We [had] waited on the ramp for an hour and a half for thunderstorms to pass over the airport. Shortly before departure we granted Scheduling a duty time extension in order to complete the flight. Also; I called clearance delivery in order to change our route toward MCO to stay clear of most radar returns. I was told that traffic was moving northward on a 020 degree heading. I relented at that point and we pressed on. If my request was granted for the reroute we most likely would have avoided the incident. If I had to do it again I would have first checked the lightning activity on the WSI app. I got a snapshot of an outflow area of a storm complex over the Gulf of Mexico taken a few days later and sure enough: valuable information on lightning occurring miles from a cell. Just supposing I had this information in my situation; I would have called Dispatch and had them advocate the route I wanted as a safety of flight issue. I have experienced more than once routing that ATC think are appropriate - where they are trying to impose their will on piloting decisions. I realize that Florida has congested airways but I wanted to share my concern for pressure this puts on us and the cost to the company with an aircraft put out of service. The lightning resource in the WSI app is something I will use when necessary to draw a more fully informed decision of the route to fly.




Synopsis: A321 Captain reported a lightning strike while flying 80 miles away from an area of dissipating thunderstorms.
Date: 201204
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Antiskid System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Aircraft; Procedure; Manuals; Incorrect / Not Installed / Unavailable Part; Human Factors; Company Policy; Chart Or Publication
Primary problem: Human Factors

Narrative: Contract Repair Station Vendor overhauls all Landing Gear assemblies for 'Time' gear change [for our Air Carrier]. Receiving Inspection required of all components. One task requires confirmation of Main Landing Gear (MLG) wiring harness routing in the axles. Found the Left-hand (L-H) MLG wiring incorrect. Outboard (O/B) harness routed to Inboard (I/B) and I/B routed to O/B position. This wiring concerns the Anti-Skid Transducers. See maintenance write-up for Corrective Action. Vendor Repaired Part.

Callback: Reporter stated his Station has started doing Landing Gear changes and Receiving Inspections of the Landing Gears for their A320/319 aircraft when they arrive from the Contract Repair Station Vendor. He works as an Inspector and does the wiring inspection prior to the landing gear being installed. After he found the Main Landing Gear (MLG) Anti-Skid electrical wiring harness cross-connected; mechanics were able to snake and reroute the harness wires without having to separate any components. The same incorrect wire routing on MLGs received from overhaul Vendors has happened before.



Synopsis: An Air Carrier Inspector; reports finding a left-hand Main Landing Gear (MLG) Anti-Skid System electrical wiring harness to the Wheel Spin Transducers cross-wired in the axles. Outboard (O/B) harness routed to Inboard (I/B) and I/B to O/B. He was performing a Receiving Inspection of the A320 MLG from a Contract Repair Station Overhaul Vendor.
Date: 201510
Local time of day: 1201-1800
Location: DFW.Airport, TX
Light: Daylight
Aircraft: MD-82
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach; Landing
Airspace: Class B DFW
ATC / advisory: TRACON D10
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Communication Breakdown; Distraction
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Landing Without Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Procedure; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: I did not call the tower before landing. I was distracted by approach telling us to be on the lookout for a [UAV] on final; and seeing three big birds above us on final just miss us.




Synopsis: Flight crew failed to call Tower and landed without a clearance due to a distraction of Approach Controller advising them about possible UAV traffic and birds on final.
Date: 201603
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff; Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After being cleared for Takeoff (TO) I began to advance the thrust levers. Before reaching an EPR of 1.1 the First Officer (FO) [and I] heard a loud 'compressor-stall' like noise (boom; boom; boom) and felt vibrations/shuddering emanating from the engines.I immediately aborted the TO and retarded the thrust levers.We had not begun the TO roll yet. We obtained clearance from tower to vacate the runway. I also asked for emergency vehicles to shadow us to the gate since I could not be sure if the engine; albeit showing normal indications at idle; was damaged.While still on the runway and taxiing toward an exit taxiway I [advanced] the thrust levers for each engine separately in order to isolate the culprit. The right engine displayed the same symptoms as previously described (boom; boom; boom; shudder/vibration) again before reaching an EPR of 1.1.After return to the gate maintenance was called and the flight subsequently cancelled. Conditions on the ground: Night VMC; light drizzle; 10 degrees C.Old planes and engines...sometimes components just don't work as advertised.




Synopsis: MD-80 Captain reported rejecting the takeoff after experiencing a compressor stall as thrust was advanced.
Date: 201912
Local time of day: 1801-2400
Location: ZZZZ.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: Tower ZZZZ
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Overcame Equipment Problem; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Split flaps on ILS going from 1 to 10. Split before 2 and stopped at 2. Missed approach with vectors and holding at PROBE. [Requested priority handling] for flight control failure. Ran checklist. TEST FA's. Rolled the fire trucks. Briefed flaps 15 landing. Used ILS and autopilot until 500 ft. Landed safely. Aircraft inspection on high speed exit by fire fighters. Taxied to the gate. Gate unaware and company not notified. FOB (Fuel on Board) at gate 6.0.




Synopsis: B737 First Officer reported that a trailing edge flap malfunction resulted in a precautionary landing.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation I/SP (C501)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
ATC / advisory: Center ZZZ
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Overcame Equipment Problem; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: My copilot and I were doing a demonstration flight at 28;000 and then on heading back to ZZZ out of 28;000 to 18;000 I noticed smoke coming out of the right side of the flight deck we immediately put on our oxygen mask and ran the emergency checklist and [requested priority handling] and headed back to ZZZ Airport and landed without any incident.




Synopsis: Citation I Captain reported a fumes event during descent.
Date: 201501
Local time of day: 0601-1200
Location: MSN.Airport, WI
Flight conditions: VMC
Light: Daylight
Aircraft: M-20 J (201) / Allegro
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Taxi
ATC / advisory: Ground MSN
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Conflict Ground Conflict; Critical; Conflict Ground Conflict; Less Severe; Ground Event / Encounter Aircraft; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Environment - Non Weather Related; Airport; Human Factors; Procedure
Primary problem: Airport

Narrative: Upon being cleared to taxi across runway 14/32 from the south ramp to the east ramp on the echo taxiway I crossed the runway and proceeded down the remaining taxiway towards the ramp. A crossing Cessna in the uncontrolled taxiway passing in front of me caused me to require stopping and pausing for approximately 10 seconds before the hold short line while they passed east bound. This in turn triggered a landing aircraft to execute a go around on runway 32. My aircraft was clear of the runway just not past the hold short line.




Synopsis: Cleared to cross Runway 32 on E to the uncontrolled East Ramp at MSN; the pilot of an M-20 had to stop short of the movement/non-movement line prior to the ramp for taxiing traffic.  An aircraft on final for 32 executed a go-around as a result.
Date: 201908
Aircraft: B767-400 and 400 ER
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Training / Qualification; Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Aircraft X returned to Gate X for Maintenance. Employee X; Employee Y and I had some sort of idea on how to address the problem. We meet the aircraft at Gate X; [I'm] on head set communicating with the flight crew. I proceeded to ask the crew to re-initialize the IRS (Inertial Reference System); with no success. Meanwhile; Employee X had requested the jet bridge to be connected to the aircraft so we can have access to the aircraft ;also power cord from jet bridge...While Partner Employee Y and someone from zone 4 Employee X ;very help I might add; were in the Electronics and Equipment compartment troubleshooting the problem. Employee Z came down from Electronics and Equipment [compartment]. Shortly after; Employee X stated from outside the aircraft that she was going UP didn't think anything of it until Employee X told me look up the hole; someone fell down through the floor access above the Electronics and Equipment compartment. Employee X had opened it without any clearance from me or anyone else; don't know what possessed her to open the hatch. General Maintenance Manual procedures. Only in remote location can we access the flight deck above; not during a live flight with jet bridge by then already connected.




Synopsis: Maintenance opened cabin hatch to electronics bay without authorization and someone fell through it.
Date: 201911
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Single Pilot; Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: Other Landing
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: The parking brake lever and heat lever knob are exactly the same; one above the other.  In-flight; the parking brake was pulled instead of the heat lever. Upon landing roll-out and actuation of brake pedals; the parking brake engaged and locked the wheels. The plane skidded in a wheel landing down the runway; as energy decreased the plane slowly rotated forward on the main gear striking the prop on the grass runway and eventually nosing over onto the cowl/nose. The leading edge outer pilots side wingtip bow also hit the ground. Corrective actions include changing the parking brake knob to a T handle or something that is identified by touch as being different; disabling the parking brake; or adding 'check parking brake off' to pre-landing checklist as it is not part of the approved checklist.




Synopsis: GA pilot reported pulling the incorrect lever inflight resulting in locking the wheel on landing and had a prop strike.