elihoole/asrs-aviation-reports huggingface dataset:
Date: 201707
Local time of day: 1201-1800
Location: ZBW.ARTCC, NH
Aircraft: Embraer Phenom 300
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZBW
ATC / advisory: Center ZBW
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Became Reoriented
Contributing factors: Procedure; Chart Or Publication; Manuals; Aircraft
Primary problem: Aircraft

Narrative: Aircraft X checked on descending to and almost level at 24000 feet RNAV arrival. I told the pilot to descend via the arrival and the pilot read it back correctly. The aircraft leveled at 24000 feet. I then saw the aircraft descend below 24000 feet prior to the fix which has a published altitude of 24000 feet. I stopped their descent; but not before they violated the underlying sector's airspace. I told the pilot the published altitude at the fix and asked why they descended early. They said the computer did it. Once they were in my airspace I gave them a descent clearance.


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


Synopsis: ZBW Center Controller and flight crew reported the aircraft descended below a published crossing restriction.
Date: 201703
Local time of day: 0001-0600
Location: LAX.Airport, CA
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower LAX
Second aircraft: B787 Dreamliner Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: We were holding; number 2; on Taxiway H short of Runway 25R at taxiway U. Tower cleared the Commuter [aircraft] and us to cross Runway 25R; at taxiway U; and contact ground on the other side. We noticed a B787 stopped on Taxiway B; short of Taxiway U facing east. The Commuter crossed the runway and turned right onto taxiway B. We followed and as we crossed Runway 25R we switched to ground. In the middle of crossing 25R; the B787 began taxiing. We had to break hard not to cause a taxiway collision. We stopped about 20 feet from the wingtip line of travel and our nose. We never heard ATC tell [the B787] to taxi and we were never instructed to hold. We queried Ground Control and they said wait for [the B787].




Synopsis: B777 Captain experienced a ground conflict with a B787 after being cleared to cross Runway 25R at taxiway Uniform by LAX Tower. Ground Control had apparently issued instructions to the B787 crew that the reporter did not hear.
Date: 201703
Local time of day: 1201-1800
Location: CVB.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Descent
Airspace: Class D SUU; Class E VCB
ATC / advisory: TRACON SUU
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation - Altitude Excursion From Assigned Altitude
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: For a visual approach to KVCB; I had been cleared to descend to 3000 MSL. Passing above KSUU's Class D airspace at 3000 MSL; I was asked by Travis Approach to notify when I had KVCB in sight. Unfamiliar with the area; I had difficulty locating KVCB but was aware I was getting very close.I mistook Vanden Road and its adjacent train track for Interstate 80; in part because in the vicinity of KVCB these routes are on opposite sides of the San Francisco sectional chart and in part because recent suburban development in the Fairfield-Vacaville area doesn't match the yellow fill on the sectional chart.As a result; I thought I was about 4nm closer to KVCB than I really was; and I began a descent. Still without the airport in sight; I neglected to advise Travis.At 2500 MSL; Travis reminded me that I had been assigned 3000. I quickly climbed back to 3000. Shortly after leveling off at 3000; I spotted KVCB; advised Travis; canceled IFR; and completed the flight.




Synopsis: GA pilot reported descending below assigned altitude during IFR flight to VCB.
Date: 201210
Local time of day: 1201-1800
Location: PHX.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Citation III; VI; VII (C650)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E P50
ATC / advisory: TRACON P50
Aircraft component: Altimeter
Component problem: Improperly Operated
Reporter organization: Corporate
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation - Altitude Overshoot; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Returned To Clearance
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: Arriving from (a high altitude airport with a high altimeter setting) into PHX (a low altitude airport with a low altimeter setting) both pilots failed to reset our altimeters to the PHX local setting causing us to cross some of the arrival fixes at lower than published altitudes. ATC advised of the lower than normal altitudes and we realized what we had done and reset out altimeters. There was no conflict with any other aircraft and ATC stated that there was no problem on their end. In turbine aircraft we reset our altimeters descending below FL180 when arriving into an airport; but since this was a short flight we never climbed that high and this got us out of our normal sequence and we missed the altitude check. We will devise a system to recheck altimeters at lower level flights in the future.




Synopsis: The flight crew of a Citation 650 failed to set the local altimeter setting on descent to PHX and; consequently; crossed some fixes on their arrival below the charted altitude.
Date: 201310
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Night
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Aircraft component: Parking Brake
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Situational Awareness; Communication Breakdown; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Other / Unknown
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Human Factors

Narrative: APU was deferred and we started all 3 engines in the blocks. I believed that the aircraft was connected to the tug. As we started the Number 1 Engine the Ground Maintenance personnel informed us that he thought the aircraft was beginning to roll. Captain applied brakes and informed ground brakes were now set and inquired as whether the chocks were removed (I believe he also asked if tug was connected but not sure). Maintenance said chocks were removed. Captain and ground calmly discussed why chocks were removed without our knowledge and why we weren't connected to tug. Continued start and departed uneventfully. I believe the miscommunication between ground and cockpit caused this event. I was absolutely certain we were connected to tug (we were not) and I am still certain we were never told the chocks were removed. The note in the external air-start saying parking brake should be set should be a warning and the ground and cockpit should absolutely know configuration of outside equipment and chocks. Any time your normal habit pattern is broken; i.e. APU deferred and external air start; you should be extra vigilant.




Synopsis: Without notice; a Cargo Maintenance crew removed the chocks before an external airstart. The aircraft then began rolling with the first engine start because the brakes were also not set.
Date: 201908
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Rejected Takeoff; Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Leg 1 of a three day pairing. Preflight; push; and taxi out were all normal. I was the FO (First Officer) and Pilot Monitoring. Captain was the Pilot Flying. We were in position on the active runway when our takeoff clearance was given. Thrust levers were brought to 40% and I was waiting for the engines to stabilize to give the 'stable' call out. Just prior to engine stabilization on COM1 which was tower frequency we heard '(airline) HIT THE BRAKES!!!' An aircraft behind us on the taxiway advised Tower on frequency that we had a '2 foot flame' coming out of the back of the Number 1 Engine. The Captain upon hearing this immediately shutdown the number 1 engine and called for the QRC. Tower wanted us to clear the runway and we advised them that we need to run a checklist and will get back to them. After running the Engine Tailpipe Fire QRC and QRH we asked Tower if the aircraft could see any indication of fire out of the engine. They said that they could not see anything. The Captain and I both felt comfortable at that point to taxi the aircraft off of the runway and onto the parallel taxiway. Airport Fire and Rescue contacted us on a discrete frequency and approached the aircraft to verify there was no active fire. After their surveillance indicating no fire the Captain and I felt it was safe to taxi the aircraft back to the gate. We advised operations and maintenance of our intentions. Taxi back and shutdown were normal.Excellent job by the Captain. Immediate decision making on his part and excellent communication. For myself personally; as always just like in the sim; slow down when accomplishing checklists. Slow is smooth and smooth is fast.I have attached a picture of the engine 'torching' as the maintenance crew were performing a run up at the gate after we returned. The engine is at idle power and the very tip of the tailpipe you can see a blue flame.




Synopsis: Aircraft flight crew experienced an engine tail pipe fire during engine spool up on takeoff roll.
Date: 201812
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Taxi
Aircraft component: Spoiler System
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Training / Qualification
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Had to perform deactivation of spoiler servo control per Minimum Equipment List. Suspect key may have been defective after lockout procedure; missing prong to return servo to O [position]. Bad tool. [We should ensure] all tools and equipment are in working condition before use.


Second narrative: During push back from ZZZ and on first engine start received a 'Flt control Fault Spoilers'. We called ZZZ Maintenance and were told to return to the gate. After some trouble shooting maintenance deferred the ground spoilers. We departed Runway XXR on the ZZZZZ [Departure] Captain's leg. After aircraft clean up and on climb out we noticed an aircraft vibration. We assumed maybe some panel or door was left open by Maintenance. Then thought about maybe one of the spoilers being out because of the MEL. Aircraft control was transferred to me; the First Officer; and Captain called Flight Attendant to go back and look out the windows to see if they saw anything. Told ATC that we would be leveling off at FL250 as climb continued and turns were done we noticed that now Alpha Prot(High Angle of Attack Protection) was increasing more than normal and now assumed that the vibration was associated with a spoiler problem. We [advised ATC] and elected to go to ZZZ1 because of long runways. ATC informed that ZZZ1 was backed up due to weather. We changed diversion location to ZZZ2. Captain briefed the flight attendants advising of the precautionary landing in ZZZ2. We ran the QRH for Over Weight Landing. On arrival into ZZZ2 we asked for long final to approach and for shallow vectors because of the increased Alpha Prot. We landed visually on Runway XX without incident. Upon arrival at the gate; I; the First Officer; went to inspect the aircraft and noticed both ground spoilers were not fully stowed. When maintenance in ZZZ2 arrived at the gate they confirmed that maintenance in ZZZ left the spoilers in what he called 'Maintenance Mode' after the deferral.


Synopsis: A321 Flight Crew and Mechanics reported maintenance had not properly completed the spoiler lockout procedure which resulted in a diversion.
Date: 201505
Local time of day: 1801-2400
Location: TAN.Airport, MA
Flight conditions: Marginal
Weather elements / visibility: Fog; 9
Light: Night
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing; Final Approach
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors
Primary problem: Airport

Narrative: Came in to land in Taunton (TAN). There was a NOTAM out for beacon out of service; not runway lights. As I approached Taunton; there were no runway lights working; just taxiway lights. I triggered the pilot controlled lighting (PCL) to try to get the runway lights to work but just saw the taxiway lights go through the low; medium; high intensity cycle. I elected that it was best given the circumstances and time to land on the taxiway. The flight terminated uneventfully. They are installing security cameras at the airport and I know they have shut the beacon off and it took 3 weeks before a NOTAM [was] issued. Now the runway lights are out of service without letting people know. There is an Instrument Approach to that runway and in an emergency situation someone unfamiliar with the field could be injured.




Synopsis: Small aircraft pilot reported TAN airport runway lights are out of service but no NOTAM to alert pilots of the outage.
Date: 201510
Location: ZZZ.ARTCC, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; Flight Crew Inflight Shutdown
Contributing factors: Aircraft; Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: Dispatcher had stepped away while OJT (On Job Training) dispatcher was on the desk. Flight notified the Dispatcher of a low oil pressure on the #1 engine. There was an attempt to patch twice and the call went to the Chief Dispatcher and the transfer failed; the second time the crew reports there was just hold music. Dispatch attempted to call and was unable to connect. Finally patch was established; when the Dispatcher returned. The engine had not been shut down and the Dispatcher and Captain agreed on return to field. The flight was near ETOPS entry. There was no oil pressure showing without the EICAS alert. Coordination of the Chief and OPS manager; MX was handled. Dispatch was waiting to hear when the engine was shut down and had the QRH out and was under the assumption that the engine would be secure shortly. The Return to field (US command) and release was completed. Sabre placed the aircraft on the ground and the dispatcher was unable to pull position reports and the ACARs were now coming into the system from the next leg from the unreleased portion of DV. It took time figure out why the system was not providing correct information.  The crew began dumping fuel from the center tank to reduce landing weight. Dispatch requested position reports to provide landing data. No position reports were sent or accepted by the ACARS requests. A time and burn calculation was done to estimate landing weights and a position report entered into Sabre to reflect the dumped fuel and new estimated gross weight. Landing data was sent and noted that this was estimated due to the lack of current fuel and position report.Once on the ground the crew reported the communication issues. They also reported that the engine was shutdown at 40NM from the field.




Synopsis: Air Carrier Dispatcher reported difficulty communicating with a flight that was experiencing an engine problem and was returning to departure airport.
Date: 202010
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: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Passenger in [seat] X1 on board appeared intoxicated and was non-complaint of wearing [a] face mask during the boarding process.Passenger in X1 on board appeared intoxicated and was non-compliant of wearing mask during the boarding process. I; the Captain; was approached in the jet bridge prior to the passenger boarding that the passenger [would be assessed] if he was fit to be on board. The passenger was allowed on board; but shortly after was removed for his non-compliance of face mask after being asked multiple times to wear it. He appeared intoxicated.




Synopsis: Air carrier Captain reported a possibly intoxicated passenger was removed from the flight for non-compliance with face mask policy.
Date: 202009
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Corporate
Operating under: Part 91
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: Corporate
Reporter function: Pilot Not Flying; Captain
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 Provided Assistance; Air Traffic Control Issued New Clearance; Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cruising at FL410; the pilot flying in the right seat noticed a small darkened section along the outside rear edge of the right windshield. Approaching top of descent into ZZZ; upon closer examination both pilots determined the darkened section of glass was actually a crack in the windshield. Instructions were received to divert to ZZZ1.




Synopsis: CE-560XL flight crew reported a cracked windshield in cruise; resulting in a diversion.
Date: 201303
Local time of day: 1801-2400
Location: LGB.Airport, CA
Aircraft: Cessna 152
Flight phase: Landing
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: A Cessna landed and did not exit the runway promptly. A second Cessna was on very short final when I noticed; and I attempted to send him around; but the pilot's lack of English comprehension caused him to land anyway; and get within 3;000 feet of the aircraft ahead. Make sure that pilots are fluent in English.




Synopsis: LGB Controller described a loss of required runway separation when a go-around clearance was ignored by a landing aircraft. The reporter claimed that a lack of English proficiency was the causal factor.