elihoole/asrs-aviation-reports huggingface dataset:
Date: 201906
Local time of day: 0601-1200
Location: DFW.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower DFW
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: After receiving clearance to cross 18R on Taxiway A and told traffic will hold short of Taxiway B we entered the runway and then the RWSL (Runway Status Lights) RED lights came on. Committed to crossing the runway I continued taxi to hold short of 18L. Traffic was on short final and pulling off Runway 18R at the time. ATC said nothing as we confirmed our clearance to hold short 18L.


Second narrative: Landed on 13R. Initial taxi instructions had us hold short of 18R at Taxiway A. Next told aircraft landing but will holding short of our intersection and cleared to cross 18R and hold short 18L. As we crossed Runway Status Lights turned on colored red. We confirmed visually no traffic and continued expeditiously across runway held short 18L and confirmed our clearance with Tower.


Synopsis: Air carrier flight crew reported Runway Status Lights illuminated while crossing runway after receiving Controller's verbal crossing clearance at DFW airport.
Date: 202104
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; 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: Other Take Off Roll
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Returned To Gate; Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Rejected Takeoff; Flight Crew Overcame Equipment Problem; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cleared to line up and wait Runway XX. When cleared for takeoff; pushed power to approximate 40% then selected TO/GA. As the thrust levers advanced; there was a very loud bang and yaw to the left. We had just started rolling. The thrust levers were brought to idle and we stopped on the runway. Initially; with the bang and yaw I thought we hit something or ran over something. As I was looking out the window; the First Officer stated we had a #1 Engine failure. Tower asked if we wanted equipment. We asked if they saw smoke or damage; and they replied 'No'; along with another aircraft on the taxiway. I made a PA for everyone to remain seated. I then called the F/A's (Flight Attendants) and asked them to look at the Captain side engine for smoke or flames. They reported it looked normal. We ran the Engine Failure Checklist; and discussed running the Rejected Takeoff Checklist. Since the event happened as the aircraft had just started to roll (probably less than 10 knots) we didn't run the Rejected Takeoff Checklist; knowing that brake energy and cooling wouldn't be an issue. After we taxied to the gate; I made calls to Dispatch; Maintenance; and the Chief Pilot on call; while the First Officer went to the ramp to inspect the aircraft. He discovered bent and broken turbine blades with metal pieces loose in the engine. He came back upstairs and called ZZZ Ground to do a runway check for engine debris. I made a PA to the passengers explaining that we had an engine failure at power up; and the aircraft would be taken out of service. They would receive more flight information in the terminal. After the passengers had deplaned; the crew got together and debriefed the event. I informed the F/As of what had happened and let them ask questions.




Synopsis: Captain reported engine failure on take off roll causing a rejected take off and a return to the gate.
Date: 201603
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Second reporter function: Dispatcher
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Procedure; Company Policy; Human Factors
Primary problem: Human Factors

Narrative: We were over fueled by 9000 pounds and did not catch the error. The fueler was having problems with fueling the aircraft and informed us over the ICS he had over fueled the aircraft by 9;000 pounds. I interpreted the number to be 900 pounds instead of 9;000; thinking it was a translation error. We sent the actual fuel on board 38.6 via ACARS which was 9.0 Thousand pounds over the plan fuel of 29.6 and the error was undetected. At takeoff I did notice the aircraft was a little nose heavy other than that the performance was relatively unaffected. After reaching cruise altitude (FL280) I did a fuel check and discovered the error. I reported to dispatch via ACARS we had been over fueled and what the actual fuel on board was. The remainder the flight was uneventful. After we landed I called dispatch and discussed the situation and was told they never received our actual fuel on board we had sent (38.6). Instead they were showing fuel of (28.6) at takeoff. This was confirmed by the load closeout which also showed fuel weight of 28.9.I'm not sure why the system did not accept the actual fuel on board we sent and then send back an alert that we had sent in a fuel load that was over what was planned. I have had it do that before.


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


Synopsis: B757-200 flight crew and Dispatcher reported the aircraft was over fueled by 9000 lbs. The Captain thought the Fueler said 900 lbs; but discovered the true amount while in cruise.
Date: 201906
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb out; approximately FL250; ECAM for generator 1 fault. First Officer did ECAM and QRH. Generator 1 would not come back online. Started APU. About 3 hours into flight climbing from FL330 to FL350 out of FL336; APU did an auto shutdown. Again; followed ECAM and QRH. Contacted [Maintenance] and Dispatch. Descended to FL290. Restarted APU. Worked fine but continued as [priority] aircraft as didn't know if it would shut down again. Uneventful landing. Met by fire trucks. Received okay and under ship's power taxied to gate.


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


Synopsis: A320 flight crew reported failure of generator #1; followed by auto-shutdown of APU. Flight continued to destination after the APU was successfully restarted at a lower altitude.
Date: 202105
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Aircraft component: Air Cycle Machine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Passenger
When detected: Aircraft In Service At Gate; Taxi
Result: Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon landing and arrival at gate a strong odor engulfed entire cabin.  Started as a manure/organic smell then changed to chemical/sulfur type smell.  Captain was notified and maintenance was called.




Synopsis: A320 Flight Attendant reported a fume event in passenger cabin during landing and gate arrival.
Date: 201310
Local time of day: 1201-1800
Location: LGA.Airport, NY
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B LGA
ATC / advisory: Tower LGA
Second aircraft: A320
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Encountered wake turbulance in landing flare from crossing departure aircraft (Boeing 737). Flying pilot corrected with quick roll command and landed.




Synopsis: CRJ-200 Captain reported wake vortex encounter on landing at LGA from crossing departure aircraft.
Date: 201401
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 60
Light: Night
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Normal Brake System
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; General Evacuated; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: The aircraft experienced a blow tire/rim lock upon landing. As the aircraft touched down; the aircraft rolled 40 FT; then; experienced an aggressive left yawing moment. At that time; I applied full right rudder and maximum right braking to counter this action. As the aircraft decelerated though VMC; the aircraft's rudder authority diminished and I was unable to maintain directional control. The aircraft proceeded to exit the runway at approximately 30 KTS where it came to rest approximately 100 FT north of the runway edge line for Runway 08L. At that time; I commanded the passengers to evacuate and 911 was called. There were no injuries to passengers or pilot. The aircraft was removed from the dirt area to a transit aircraft ramp that morning. The aircraft was on speed; on target; under max landing weight and within weight and balance limitations. The aircraft had both tires replaced six days prior by a Cessna repair station due to wear limits. Approximately 10 cycles between the repair and the incident accumulated. Maintenance personnel did not advise of any wear limit issues when the aircraft was picked up. Brake pad limits were expressed with Cessna upon pre-buy inspection but Cessna elected to only replace the right main landing gear brake. Upon pre-flight inspection that morning; I noted no abnormalities with the braking system. Cessna mechanics found brake pads to have aggressive wearing on the left main tire causing the wheel to freeze upon landing. The aircraft is currently being repaired by Cessna. Left brake pad; left wheel and tire needed to be replaced. No other known damage to the aircraft.




Synopsis: CE525 Captain experiences a locked brake after landing and loss of directional control; resulting in a runway excursion at low speed. The right brake pads had been replaced six days prior; but not the left; although post flight revealed extreme wear on the left brake (the locked wheel).
Date: 202010
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Other Unknown
Operating under: Other unknown
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Staffing
Primary problem: Staffing

Narrative: FL370 enroute from ZZZ to ZZZ1; we encountered an Air Traffic Controller that was clearly over saturated because of multiple frequencies or too many aircraft.  Traffic in these 2 areas are returning to normal.  We need more Controllers and frequencies to avoid safety of flight issues.




Synopsis: Captain reported concerns about safety of flight issues due to ATC controllers being under staffed and overworked while having to work multiple frequencies.
Date: 202111
Local time of day: 1801-2400
Location: SBN.Airport, IN
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operating under: Part 91
Flight phase: Taxi
ATC / advisory: Tower SBN
Second aircraft: Commercial Fixed Wing
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Equipment Issue; Ground Incursion Taxiway
Detector: Person Air Traffic Control
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Airport
Primary problem: Airport

Narrative: Aircraft X was assigned a right turn onto Taxiway A3 after landing roll. Aircraft X turned onto the closed Taxiway A4 instead which resulted in me sending around an air carrier. Shortly after this incident Operations called me to inform me that there was no signage to indicate to pilots where Taxiway A3 was. There are numerous taxiway closures due to construction and this has made our airfield configuration very complex at times. I highly recommend more signage to help out both the controllers and pilots to not get confused. The number one contributing factor was the pilot not having adequate signs to know where he was going.




Synopsis: SBN Local Controller reported an aircraft exited on wrong taxiway; resulting in the Controller sending traffic around.  Reporter was notified that there is a lack of Taxiway A3 signage due to construction.
Date: 201704
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Oxygen System/Crew
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Human Factors

Narrative: I swapped into this aircraft and I tested the oxygen mask in accordance with the Canadair SOPM; and coincident with actuation of the TEST/RESET lever the  CREW OXY LO PRESS caution message posted. The message disappeared when I released the TEST/RESET lever. Since the gauge indicated approximately 1500 psi; I contacted Line Maintenance to resolve this discrepancy. Line Maintenance discovered that the crew oxygen shut-off valve was in the closed position; meaning that no oxygen was  available to the crew masks. The valve was opened and we were returned to service.Failure of maintenance up-line to open the crew oxygen shut-off valve. Maintenance: Verify task completion. Flight Operations: Revise the Canadair Standard Operating Procedures Manual; to include verifying that the CREW OXY LO PRESS caution message is not presented during the oxygen mask test. Coincident with issuance of the temporary revision; issue a Flight Operations Alert Bulletin for pilot awareness.




Synopsis: CRJ-200 Captain reported discovering during preflight that the crew oxygen supply was turned off at the bottle.
Date: 201502
Local time of day: 0601-1200
Location: DVT.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Gulfstream IV / G350 / G450
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground DVT
Reporter organization: Corporate
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer
Human factors: Situational Awareness
Anomaly: Ground Excursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airport; Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: After normal preflight and engine start operations we received a taxi clearance. Paraphrasing; taxi to RWY 25L via Taxiway A; A13; hold short of RWY 25L. It was the taxi clearance we expected and briefed. As we started the taxi we commenced with the taxi checklist. The taxi checklist was completed. As we approached the 90 degree turn from Taxiway A onto Taxiway A13 we discussed the narrow taxiway and the tight 90 degree turn. During the turn; even though we favored the left side of the taxiway; the right main wheel went off the taxiway. We contacted ground control for assistance.  Suggest an Airport Operations  review of the DVT intersection of Taxiway A and A13.  Convergence of two narrow taxiways.  The inside of the turn is not a smooth arc for transition from Taxiway A to A13. The old   taxiway had a smooth arc inside of the turn.  The taxiway markings are at the very edge of the taxiway with no hard surface margins. The old   taxiway had hard surface outside of the taxiway markings creating a margin.For narrow taxiways the crew should use the onboard cameras for situational awareness for wheel/edge proximity.




Synopsis: G450 First Officer experiences a taxiway excursion at DVT during a turn from Taxiway A to A13. The right main gear departs the paved surface during the turn.
Date: 201902
Local time of day: 1201-1800
Location: SJT.Airport, TX
Flight conditions: VMC
Weather elements / visibility: Cloudy; 10
Light: Daylight
Aircraft: Small Transport
Operator: Air Taxi
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Taxi
Airspace: Class D SJT
ATC / advisory: Tower SJT
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Communication Breakdown
Second reporter function: First Officer
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Airport; Procedure
Primary problem: Airport

Narrative: After landing Runway 3 at SJT; we were taxiing on Runway 27. I believe the tower told us to hold short of Runway 18. As we approached 18 we looked down final and did not see the white colored light aircraft on short final. He was difficult to see with the overcast skies. Tower contacted me right after we crossed and I saw the light aircraft on the runway about 1;000 feet from our crossing point.There appears to be a miss-understanding of some sort on my part of the clearance.If I may ask a question; are there supposed to be painted markings on a runway crossing another runway?


Second narrative: My first flight in [this aircraft] doing training exercises to prepare me for SIC. I just landed my second ILS on Runway 3 at SJT. We copied to taxi on Runway 27 and hold short Runway 18. PIC was taxiing. There was confusion about where the hold short line was for Runway 18. It was overcast and didn't see traffic until we crossed 18. Traffic was 1;000 feet away and wasn't a factor. I believe there was poor communication in the cockpit and could be corrected with cross reference clearance from both pilots and a reminder from tower of this unusual hold short circumstance.


Synopsis: Air taxi flight crew reported while taxing; ATC issued a hold short clearance at intersecting runways with no identifiable hold short marking; resulting in a runway incursion.
Date: 201210
Location: MMMX.Airport, FO
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
ATC / advisory: TRACON MMMX
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Training / Qualification
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Procedure; Human Factors; Chart Or Publication
Primary problem: Human Factors

Narrative: Flight operating on an ICAO descent via clearance; ATC issued a new altitude to descend to but did not specifically cancel star altitude constraints. Confused with the differences between the FAA and ICAO descend via clearance requirements (FAA needs to re-issue descent via for constraints to be in effect; ICAO does not) we descended below the star constraints. Additionally; later on the flight; during approach; the pilot flying failed to operate below the speed limits [160] established for Mexico's airspace and for the Runway 5R ILS approach.




Synopsis: Air Carrier First Officer reports confusion descending into MMMX over RNAV descent criteria for ICAO vs. FAA. The 160 KT speed restriction on the ILS 5R approach is also overlooked.