elihoole/asrs-aviation-reports huggingface dataset:
Date: 202105
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Cockpit Window
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Distraction; Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While in cruise phase at 35;000 feet the Captain who was the Pilot Monitoring at the time noticed a small crack in the left windshield. Upon recognizing the situation the Captain immediately took the aircraft controls; instructed me; now the Pilot Monitoring; to advise ATC that we are executing a descent. I complied with the Captain's instructions and we told ATC that we were descending to 10;000 feet and diverting to ZZZ which was approximately 40 miles away at the time. At this time the Captain continued to fly and talk to ATC while I called operations at ZZZ to let them know we were coming. After this we set up for the ILS XXL to back up the visual since the weather was VMC at ZZZ. We executed all normal checklists and the Captain executed an uneventful approach and landing. We taxied into the ramp and the Captain shutdown and inspected the exterior in the vicinity of the window and passenger door on the left hand side to ensure it was safe to deplane. ZZZ fire rescue also confirmed that we required no further assistance. Passengers were deplaned and aircraft was secured. Cause unknown. Suspected micro crack and heat/cool cycles.




Synopsis: CRJ-900 First Officer reported the windshield cracked while in level cruise.
Date: 201510
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Training / Qualification; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Load Planning called approximately 1 hour before arrival EDDF to advise they weren't sure exactly what was on the aircraft; due to confusion on the ramp with another EDDF flight. I relayed this information to the crew. They replied no handling problems with the aircraft; slight fuel overburn; but that's not unusual.  However; this is an unsafe operation. Positive verification of loading is required prior to issuing final weights.




Synopsis: Air carrier Dispatcher reported being advised by Load Planning that they were unsure of what was loaded on two flights departing for Frankfurt.
Date: 201903
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Aircraft component: Intake Ice System
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: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Received this aircraft in ZZZ; where the Local Maintenance told me the #3 Bleed HP Valve had to be secured shut because the wire going to the switch that operates it was faulty. In cruise from ZZZ to ZZZ1; we got a bleed 3 advisory message; ran the appropriate QRH procedure and landed without incident. Upon arrival to ZZZ1; we wrote it up and figured it was associated with the HP valve. The message was cleared and eventually we left for ZZZ2. During climb out; once again the message reappeared; and this time when we ran the procedure it was determined we would not have anti-ice on the #3 engine. We had not yet coasted out; so I contacted Dispatch and Maintenance via SATCOM so we could figure out what the best course of action would be. After an extensive discussion; weather analysis and input from Captain. It was determined we would be ok to continue to ZZZ2. This was a very time; resource and energy consuming situation which in my view could have been easily handled if we had just nipped it in the bud. This aircraft was being routed ZZZ-ZZZ1-ZZZ2-ZZZ3-ZZZ4; where in ZZZ4 it is going in for a C Check. I feel there was the feeling of just pushing it to get it to ZZZ4 where the issues would be resolved at the check. In the end; the Aircraft ended up being delayed in ZZZ2 for this and other issues which came to light during our flight to ZZZ2.




Synopsis: B747 Captain reported repeat issues with an engine bleed valve that impact the engine anti-ice system.
Date: 201501
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Cruise
Airspace: Class A ZZZ; Class E ZZZ
ATC / advisory: Center ZZZ; TRACON ZZZ
Aircraft component: Transponder
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Workload; Confusion; Distraction
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft RA
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Became Reoriented; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After departing we were being vectored when we got an RA. We responded by executing a 1G downward pitch as directed by the TCAS Prompt. We reported RA to ATC; who had no traffic within 10 miles. TCAS indicated anon transponder equipped target was +200 feet above us. I never saw the traffic in question. In addition; the TCAS alert was nonstandard as it called 'traffic; traffic' but commanded us down; indicated on the ADI. We climbed back toward the altitude assigned. We never got a clear of conflict message. The RA simply disappeared.After leveling in cruise; we got another RA with this time a 'descend; descend' prompt and ADI indications for another no transponder equipped aircraft. We could not see and aircraft and ATC had no target. RA continued for 3-5 minutes until it disappeared. We contacted maintenance; wrote up the A/C and deactivated TCAS.




Synopsis: Shortly after a B757 departed the TCAS began reporting an RA with no traffic in the area. The alert ceased and the crew climbed to cruise altitude where another phantom RA event alerted. A null bus fault was assumed.
Date: 201511
Local time of day: 1201-1800
Location: JFK.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B NYC
ATC / advisory: Tower JFK
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: While on short final for runway 31L at 1500 feet; a drone/UAV was headed straight for our aircraft at a bearing of 135 at a high rate of closure and barely missed us. My first officer was the first to spot what he first thought was a collection [of] balloons emerging from the runway 31L center line. As the object got closer we saw that the object was some sort of diamond-shaped drone with a single pusher prop behind it. The drone passed less than 50 feet directly over the nose of our aircraft where we got a good look at it. We reported the encounter to Tower. They tried; but could [not] successfully track the vehicle on radar.   This drone incident was a great concern to me compared to the other encounters reported by aircraft this year for a variety of reasons. First; was the deliberate nature of the drone's operator in heading right for our aircraft down the center line of a major US airport runway in a difficult political climate.Next; was the type of drone used. This drone was not your typical four-rotor toy as in previous encounters. The four to five foot fixed-wing; diamond-shape; stealthy police/military style fuselage; with short; blended; delta wings and down sloping winglets; had a belly mounted camera globe. This was closely related to an upgraded 'Killer Bee (or Bat)' drone I once spotted during my time as an aviator in the military. Finally; I was concerned that ATC had no ability to track this larger UAV and find those responsible.   We need more visual binocular scanning from tower; rather than relying on Airport Radar which doesn't seem to pick up drones of the size and type I encountered. [Authorities] recommended to me that a pilot should hit the ident button on the transponder when you see a drone coming in close proximity to your aircraft. He said it helps ATC better pinpoint the location of these small vehicles.




Synopsis: A CRJ-900 on short final to JFK airport had a near miss with a UAS similar in appearance to the Raytheon Killer Bee.
Date: 201811
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Ramp
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General Work Refused
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: Bag arrived in ZZZ with smart bag in cargo from ZZZ1...ramp refused bag in ZZZ to ZZZ2.




Synopsis: Ground personnel reported removing arrival smart bag and refused to load on connection flight to destination.
Date: 201910
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: RPM/N1/N2/Etc Indication
Component problem: Improperly Operated
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Training / Qualification; Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Maintenance; Person Flight Crew
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Procedure; Human Factors; Incorrect / Not Installed / Unavailable Part; Logbook Entry
Primary problem: Incorrect / Not Installed / Unavailable Part

Narrative: Aircraft X came to ZZZ with a Pilot Discrepancy for Engine 1 EPR Mode Fault. Found short P/T2 probe installed on Engine 1 nose cowl. This part is incorrect for A321. Engine 1 P2/T2 probe was replaced in ZZZ1 by contract Employee. Discrepancy was corrected by [company] mechanics in the ZZZ hangar. I was not involved with the repair; but was made aware of the event.Event occurred in ZZZ1 by contract maintenance. It was discovered that the incorrect probe was installed when Aircraft X arrived in ZZZ. Task Card 'Remove-Install Nose Cowl' explains the different probe effectivities. The reference material is very hard to follow to understand effectivity. There needs to be a more direct way to verify effectivity on engines.




Synopsis: Technician reported aircraft released for service with wrong part installed.
Date: 201901
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Object; Ground Excursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented; Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After crossing XXR on taxiway X3; I started my pre-takeoff briefing; the First Officer went heads down to verify the departure in the FMC. Instead of starting my turn to taxi between the blue taxiway edge lights I turned to line up with outer edge lights under the aircraft. It was an optical illusion with the width of pavement I confused the edge lights as taxi lights. As soon as I started towards the edge lights I realized the mistake I was making and corrected back to the taxiway center. By that time I had hit two of the lights with the outer left main tires. We returned to the ramp and had the aircraft inspected. Rest of flight was normal.




Synopsis: B767 Captain reported losing situational awareness during taxi resulting in taxiway excursion.
Date: 201511
Local time of day: 0601-1200
Location: DFW.Airport, TX
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
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: Descent
Airspace: Class A ZFW
ATC / advisory: Center ZFW
Second aircraft: B737-800
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Flight Engineer
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Environment - Non Weather Related

Narrative: Descending on the BOOVE3 RNAV arrival into DFW from GUTZZ intersection; we were following a B737-800 on same arrival that was approximately 10 miles ahead. With a 35-40 knot tailwind from the southwest; we began to experience uncommanded rolls; some rather abrupt as the arrival altitudes narrowed. I disconnected the autopilot & continued the arrival parallel & just east of the RNAV course to stay outside the lead aircraft's wake. We notified Ft Worth ATC of the event & our intention to stay just east of course to maintain slightly upwind of the B737's wake.Winds aloft basically aligned with the northeast direction of this arrival; also with the precision of today's RNAV SIDs & STARs; these events are no longer random; but are occurring with any RNAV arrival that lines up with the winds aloft. Events range from a momentary 'thump' over a turn at an intersection; to longer duration events such as above. Also; the B737-800 and -900 series aircraft are slightly heavier than the MD80s & a different wing design; which I believe is a contributing factor.




Synopsis: MD-80 First Officer reported encountering wake turbulence in trail of a B737-800 on arrival into DFW.
Date: 201204
Local time of day: 1201-1800
Location: ZLA.ARTCC, CA
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight phase: Cruise
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Aircraft component: FMS/FMC
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Commercial
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Shortly after departure; talking to LAX Center got an 'RNP' flag in both PFD's. During our evaluation of the problem and verifying our position; LAX Center called and questioned our position and gave us a heading. Informed ATC our FMS wasn't working properly and changed our flight plan designation.


Second narrative: We flew the rest of the fight using VOR to VOR navigation (old school). Flight landed uneventfully.


Synopsis: An MD-80 flight crew reported a malfunctioning FMS to ATC; and they flew VOR-based navigation to destination.
Date: 201808
Local time of day: 1801-2400
Location: MDW.Airport, IL
Flight conditions: IMC
Weather elements / visibility: Turbulence
Light: Night
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E C90
ATC / advisory: TRACON C90
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Regained Aircraft Control; Flight Crew Took Evasive Action
Contributing factors: Weather
Primary problem: Weather

Narrative: Aircraft encountered severe turbulence over PNT VOR while in the turn to JOT VOR. The aircraft banked 45 degrees due to turbulence; Bank Angle Warning sounded and autopilot disengaged. The aircraft lost 200 feet to 500 feet of altitude; and heading was 30 degrees off course to avoid additional turbulence. ATC was notified of event and further instructions were to fly direct CADON when able. [The] rest of [the] flight was uneventful.I could see the frontal system ahead of us on radar and it appeared we would stay clear of weather over PNT. Ten miles prior; I queried the First Officer to ask for 20 degrees right. The First Officer was unable to get a clearance due to heavy radio congestion. We stayed on vector and subsequently encountered the turbulence. I should have used my emergency authority to begin the turn prior to ATC clearance but due to compressed vectors in and out of weather; I wasn't quick enough to react to the situation.


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


Synopsis: Air carrier flight crew reported an encounter with severe turbulence.
Date: 202006
Local time of day: 1201-1800
Location: HPN.Airport, NY
Flight conditions: VMC
Light: Daylight
Aircraft: Small Transport
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class D HPN
ATC / advisory: TRACON N90
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Environment - Non Weather Related; Human Factors; Staffing; Airport
Primary problem: Staffing

Narrative: SIC obtained a hold for release clearance; and loaded the FMS.  Reviewed FMS programming per FOM/AOM verified all the points.  SIC stated we were given a SID then as filed.  While proceeding on our route; ATC cleared us to a fix that was not on our flight plan.  Queried ATC as to our routing; and it did not match our as filed routing. (Filed ZZZZZ JXXX ZZZ1 ZZZ2 JXXY ZZZ4;  believe ATC said clearance was ZZZZZ JXXX ZZZ3 direct ZZZ4).  Asked ATC for a heading while we corrected our FMS programming.  ATC cleared us to another fix; verified the routing to destination.  We adjusted the routing and proceeded to our destination.Re-opening the ATC facilities at HPN would be helpful; especially with the increasing amount of flights into and out of HPN.




Synopsis: Pilot reported clearance was different than what they had filed and would like to see HPN ATC Facilities re-open.
Date: 202201
Local time of day: 0001-0600
Location: ATL.Airport, GA
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Ground ATL
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Distraction
Anomaly: Conflict Ground Conflict; Critical; Ground Event / Encounter Vehicle
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Taxiing from gate; approaching A7; ATL Ground cleared us A7 A 26R; taxi speed 15 kts. Fire Truck approaching from the right; high rate of speed crossed in front of us on service road. If I had not stood on the brakes a collision would have occurred. Fire Truck never slowed. Explained the situation to Ground Controller and said that it happens a lot. Fire Truck was returning to station. Did NOT have emergency lights on. Fire Truck driver ignoring ground procedures. Have fire truck driver abide by ground vehicle rules.




Synopsis: Pilot reported a ground conflict with a fire truck that sped past them without lights on.