elihoole/asrs-aviation-reports huggingface dataset:
Date: 201407
Local time of day: 0601-1200
Location: ZLA.ARTCC, CA
Light: Night
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness; Confusion
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Airspace Structure

Narrative: Aircraft X was under the control of SoCal TRACON; Arrivals area; when it entered Sector 21 airspace west of PDZ passing through 16;500 (I own 140 and above; SCT owns 130 and below) without a point out.  This same aircraft also entered Area B; Sector 18's airspace without a point out.  This is simply one example of a systemic problem with LA arrival traffic on the mid shift not being pointed out from the SCT Arrivals area to Area E.  Again; this issue exists only on the mid shift; not during the day.I have personally attempted over the last year to resolve this issue in a more friendly and informal manner by trying to work outside official channels (i.e. communicating with controllers from SCT outside work; having a FLM that used to work there reach out to someone they knew; all in the effort to keep things friendly) but the problem persists.  Other controllers who work mid shifts on other nights of the week are having the same issues.  I don't know what else to do at this point other than to file this report.If the traffic is not being kept inside SCT airspace; we would like to receive a point out on the traffic.  After reviewing the LAX Redeye 2 STAR; it seems that the problem is that the altitudes on the STAR do not contain the aircraft within the vertical limits of SCT airspace.  As a result; whatever clearance is being issued by SCT (descend VIA? some other crossing restriction?) results in an airspace deviation if the aircraft doesn't start down early or if the controller does not manage the descent with some other clearance to keep the traffic inside their airspace.  Re-working the altitudes of the STAR to contain the traffic within SCT airspace would be a longer-term solution.




Synopsis: ZLA Controller reports of airspace violations that happen on the mid-shift with SCT controllers violating ZLA's airspace.
Date: 202105
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing; Taxi
ATC / advisory: Tower ZZZZ
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: Communication Breakdown; Workload
Second reporter function: Pilot Flying; First Officer
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: First Officer's landing. After touchdown and roll out to the end; we were issued taxi instructions while still on the runway and during transfer of control from FO to Captain for taxi. I heard taxi Alpha to the gate which I read back. As we turned across the hard stand for gate X from Alpha the controller informed us we had been instructed to taxi Alpha Fox. [The cause was] Task saturation. Controllers should not issue taxi instructions until clear of runway. Busy airports should have a standard and understood initial taxi route so that you have time to clear the runway and listen to further instructions. Maybe they could be depicted on the approach plate or in the airport diagram or the controller could issue with landing clearance.


Second narrative: On the landing roll out while we were transferring controls we were issued a taxi clearance to gate X. The Captain still had the radios as we were decelerating through about 80 knots. He responded to the radio call and I can clearly remember him saying taxi to the gate via Alpha. There was no correction from ATC so we taxied to the gate. As we crossed the ramp area the Controller advised us the instructions were Alpha Echo Foxtrot. We apologize and proceeded to the gate with no further issues.The inability to hear the controllers instructions clearly at a busy time in the landing roll out combined with the lack of correction by ATC when our read back was incorrect. In the future I will restate the instructions from ATC once I have the radios on the ground after the roll out is complete. I will also plan not to respond the ATC during task saturation like this.


Synopsis: Air carrier flight crew reported a taxiway incursion occurred after ATC issued taxi instructions while the aircraft was still decelerating on the landing roll and the crew was unable to hear instructions clearly during that 'busy time.'
Date: 201912
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
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: Failed
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: 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 Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During the cruise phase of flight at FL290 about 20 nm from the ZZZZZ Intersection; the front windshield on the Captain side has been shattered and cracked. I have taken the oxygen mask; googles and establish communication; advised ATC and took the controls - started descent to the safe altitude; we have gotten priority from ATC and straight on course to ZZZ. As soon we have done with the QRH and checklists I have transferred the controls back to the First Officer for a landing to the field; as my view was very limited due to the broken windshield. After landing; we were checked for safety reasons by Ground Personnel and taxi to gate and deplane normally.




Synopsis: CRJ-700 Captain reported that a windshield cracked during cruise resulting in a diversion.
Date: 201904
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On departure; we encountered a strong smell in the cockpit. Within a few minutes smell disappeared and we chose to continue the flight. On arrival into ZZZ1 we got the smell back and along with haze. We talked to Maintenance and wrote up the airplane. We think it was a bleed issue. We decided to continue after the smell dissipated but realized there was more of a problem when it returned. We chose the best option that we could per the situation.




Synopsis: EMB-145 Captain reported strong smell in cockpit on departure which dissipated. Odor and haze returned on arrival at destination.
Date: 201511
Local time of day: 1801-2400
Location: DCA.Airport, DC
Light: Night
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B DCA
ATC / advisory: TRACON PCT; Tower DCA
Second aircraft: Medium Large Transport
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Distraction
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: Other Post Flight
Contributing factors: Human Factors; Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: This is a follow up to [another report]. The QC (Quality Control) department finally investigated this possible compression error. Seventeen days after the event DCA tower was asked whether they were providing visual separation during this event. They asked the controller involved at DCA tower and they said that they had both aircraft in sight and were providing tower visual separation. As far as I know the investigation is closed without a loss of separation involved. Unless someone has a photographic memory; this seems ridiculous. Obviously the investigation outcome is a cover-up of the OM's responsibility to timely investigate all reported losses of separation reported to them by the area FLM/CIC.




Synopsis: PCT Controller reported of a problem that happened 17 days prior. The question was; what type of separation was being used. Tower controller reported visual separation after being asked. Reporter thought this was a cover up for the lack of a timely investigation.
Date: 201506
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-24 Comanche
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Brake System
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Conflict Airborne Conflict; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Flew to approximate location of the outer marker. Tower cleared me to land [Runway] 17R. Turned to 17R but there was another aircraft landing on 17R. Lined up for Runway - Gear was down; etc. then Tower said turn left 30 degrees and I turned left. A third plane came on the frequency. Tower instructed me to go to 17L. I have no idea why I was not allowed to continue & land on 17R; as I was already on Final. Turned for 17L and lined up with the water runway With the reflection it looked like a Paved runway. Advised tower of my mistake; - then advised that I would go to runway 17L. Landed a little long; hit the toe brakes and was all over the place. Then tried the hand brake; and was all over the runway still. No braking effect at all. Did not realize that the right brake was not working and that the left brake was working.Then held hard on the hand brake and went left into the ditch. We had on seat belts and shoulder harness which held us.




Synopsis: The pilot of a Piper Comanche experienced a loss of braking control during landing rollout resulting in a runway excursion.
Date: 201305
Local time of day: 1201-1800
Location: ORD.Airport, IL
Flight conditions: VMC
Light: Daylight
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ORD
Second aircraft: Embraer Jet Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Human factors: Communication Breakdown; Distraction; Situational Awareness; Time Pressure
Second reporter function: Captain; Pilot Flying
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Aircraft
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Environment - Non Weather Related; Airport; Human Factors
Primary problem: Ambiguous

Narrative: Taxied from the gate. Was told to taxi via A and hold short of E to allow an Airbus to pass on Bravo from left to right. We were not completely on Alpha even though our clearance allowed us to be on Alpha. Was holding short of Echo when a commuter jet approached from our right on Taxiway Alpha. Our brakes were set and we did not think there was enough room for the commuter jet to clear our nose. We waved frantically and flashed all of our lights at the pilots to stop. The commuter jet stopped just abeam our nose. The ATC Controller apologized for the conflict. My company sent wing walker out to make sure the commuter's wing cleared our nose. We shut down both engines for safety.


Second narrative: [This narrative contains no addition information]


Synopsis: A widebody stopped short of ORD Taxiway A with clearance to hold short of E and while stopped a commuter jet approached and stopped because it could not pass in front the widebody.
Date: 201709
Location: ACK.Airport, MA
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ACK
Reporter organization: Air Taxi
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport
Primary problem: Airport

Narrative: A dangerous situation exists at ACK; Nantucket Memorial Airport. The ramp area controlled by the FBO is highly congested; poorly marked; and uncontrolled. Usually the only directions for parking are received via radio regarding where to park. There are no taxi lines; no follow-me vehicles; and usually no ground guides. Aircraft are parked haphazardly with minimal clearance to taxi past. This condition exists both during arrival and departure. This is the worst ground parking situation in the nation.




Synopsis: Air taxi First Officer reported the ramp area at ACK is very congested; poorly marked; and uncontrolled.
Date: 202008
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Environment - Non Weather Related; Human Factors; Staffing
Primary problem: Staffing

Narrative: I was working the Local Control East and West position combined; south operation; landing Runway XXR and Runway YYL; departing Runway XXR and Runway YYR.  Aircraft X checked in on final approach to Runway XXR and was cleared to land. I continued with the duties required of me at the time when the conflict alert alarmed. I processed the information as quickly as I could (overlapping tags); then immediately began to issue traffic while realizing the conflicting aircraft had passed east of my traffic.Keep a SUP/CIC in the Tower not combined with any other position to help scan the movement areas and assist as needed. Although; we are working half the traffic that we are accustomed to; complexity is added due to the combining of positions; runway; and taxiway closures; numerous vehicle calls due to airport construction. Due to the global pandemic we are already working short staffed; so I would not recommend taking a needed body off a crew to accommodate leave on another shift.




Synopsis: Tower Controller reported an airborne conflict between an IFR arrival and a VFR aircraft while working combined Local positions.
Date: 201709
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain; 6
Light: Daylight
Aircraft: Learjet 55
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Electrical Power
Component problem: Failed
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During descent; the Primary and Secondary inverter annunciators illuminated constituting a total loss of aircraft electrical power. At this point we [notified ATC] as we were IFR with no quick option of escaping the instrument conditions [and] requested vectors to the nearest suitable airport. Approach assisted with great efficiency [and] we were vectored onto the ILS. During this time; the First Officer was completing all necessary checklists while I handled the radios and aircraft. Once cleared for the ILS on a gentle vector to the course we flew a normal approach to landing getting visual Identification of the runway at 1200 FT AGL.




Synopsis: LR-55 Captain reported diverting to an alternate airport after experiencing loss of all electrical power.
Date: 202109
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
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; Procedure
Primary problem: Procedure

Narrative: Was cleared by ramp tower controller to enter the ramp at [taxiway] 1 for parking at gate X.  Approaching South on [taxiway]1 just prior to the ramp entrance; I observed a fuel service truck moving from the left of the aircraft traveling at a high speed moving East to West.  I applied the aircraft brakes to abruptly stop aircraft motion forward in order to prevent a possible collision with the ground vehicle.  I immediately informed the ramp tower controller of the vehicle hazard and asked if they could see the vehicle.  The controller asked me for a vehicle number which I could not provide due to the speed at which the ground vehicle was moving and my priority of stopping the aircraft to avoid a potential conflict.  I provided the controller with the position that I observed the truck as it sped past the tail of a B787.  The controller provided no assistance and seemed inconvenienced by my request even though there were virtually no other aircraft movements underway at this time....it was not busy.  I proceeded to gate X and parked the aircraft per normal operations.




Synopsis: Captain reported having to abruptly stop the aircraft due to a high speed fuel truck moving near the aircraft.
Date: 202108
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise; Parked
Airspace: Class A ZZZ1
ATC / advisory: Center ZZZ1
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Just prior to pushing; I was handed a Notice to Crew (NOTAC) for aircraft batteries in compartment D. I signed one and kept it; signed the other and returned it. I didn't look at it closely and didn't realize until cruise that the release was supposed to note it as well.




Synopsis: B737-800 Captain reported aircraft departure with flight release missing required 'Hazmat cargo' amendment note.
Date: 201405
Local time of day: 1201-1800
Location: EWR.Airport, NJ
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B EWR
ATC / advisory: Tower EWR
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were flying the Stadium Visual to RWY 29 EWR in clear conditions.  We crossed GIMEE at 2;500 feet and then did a constant descent towards SLIMR and CHUMR. We didn't notice that the FMGC alt at SLIMR was 900 feet instead of the recommended 1;500 feet.  We were fully configured for landing at SLIMR and I was trying to locate visually the surface references on the chart since it was a clear and unobstructed day. It was starting to look low so we stopped the descent and about that time the Tower asked us to check our altitude. We were about 700 feet at that time and stayed level and fully configured until we intercepted the PAPI's for 29 and made a normal landing. It was bright daylight and we could clearly see everything around us and felt it was safe to continue.  I think we crossed SLIMR intersection at about 500-600 feet lower than the recommended 1;500 feet.




Synopsis: An A320 flight crew descended below the recommended crossing altitude during a published visual approach; and as they noticed the error they were additionally warned of the low altitude by the Tower.