elihoole/asrs-aviation-reports huggingface dataset:
Date: 201905
Local time of day: 0601-1200
Location: ZZZ.ARTCC, FL
Light: Daylight
Aircraft: B737-800
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: Main Gear Tire
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Air Traffic Control
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: During climbout at approximately 20;000; ATC advised that ZZZ Tower reported rubber deposits on runway. Only cockpit indication during takeoff; around 100 kts; was an anti-skid light on the auto brakes. Checked system status page and noticed a slowly decreasing 'A' hydraulic system. Ran several QRH checklists and continued to ZZZ1.Briefed flight attendants and passengers. [Requested priority handling] with ZZZ1 and opted for low approach to get assessment of tire conditions of left main gear.Returned for uneventful landing; stopping on runway for ARFF (Airport Rescue and Firefighting) inspection. Maintenance pinned gear and towed us to gate.




Synopsis: B737 Captain reported that ATC advised them of rubber deposits on the runway after they left; crew ran checks and landed at destination; with a tow to the gate.
Date: 201809
Local time of day: 0001-0600
Location: ORD.Airport, IL
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ORD
ATC / advisory: Tower ORD
Second aircraft: A319
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; 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; Procedure
Primary problem: Procedure

Narrative: We were departing out of Runway 22L. We were given line up and wait after an A319. After the A319 lifted off we were given clearance to take off with a turn to the south. The configuration of the airplane was Flaps 8 and no flex. Everything was normal until we reached 150-200ft. That's when we caught the wake turbulence of the A319. At that point we were getting a stall shaker. I was maintaining my attitude as close as possible to the flight director and we exited the wake turbulence at about 400 to 500 feet. I think that Chicago needs to better separate the aircraft on takeoff especially depending on the size of the aircraft.




Synopsis: CRJ-200 Captain reported encountering wake turbulence departing ORD in trail of an A319.
Date: 201304
Local time of day: 0601-1200
Location: HOT.Airport, AR
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Bonanza 35
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Climb
Airspace: Class E HOT
ATC / advisory: CTAF HOT
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: Hot Spring airport conducted an open house. There were several visiting aircraft of various types; helicopters and displays. Horse races were going on at the race track in Hot Springs. Our local pilot club offered flights to young members. There was no overall pilot briefing. Our club pilots briefed each other as to the typical flight route over common sites around the area along a 5 mile border of the airport. Winds favored Runway 23 and was the accepted choice. The typical club pilot route was to take Runway 23 climb straight out to 1;100 FT MSL or higher (HOT is 540 FT MSL); which is over Lake Hamilton (not over residences); start a left climbing turn to 180 degrees continue climb toward the 5 mile south end of Lake Hamilton; then turn east continuing climb to 2;000 FT MSL. Then continue east to Carpenter Dam (still out the 5 mile border); then turn north to Magic Springs amusement park starting a descent to 1;500 FT MSL; turning left to 230 degrees commencing a 5 mile straight in final to Runway 23. Local landing traffic would be well inside that routing. Position announcements were made over each fix on CTAF. On my third trip I announced 5 miles south over Lake Hamilton turning east climbing to 2;000 FT MSL passing through 1;500 FT MSL. An aircraft (unknown type) responded 'Yes; you just flew 200 FT below me!' I have to assume he was above and behind me. I never saw him nor had any notice of his inbound status. Since I was east bound I did not see him on the downwind leg. Assumption is he was on a 45 degree downwind entry for Runway 23 and descending to 1;500 FT MSL pattern altitude. The pattern was quite active with various aircraft making multiple announcements. The flight continued without incident. I do not believe I committed any violation. Any action on my part was inadvertent and not deliberate.




Synopsis: BE35 pilot is informed of a NMAC by the other aircraft involved while climbing to 2;000 FT 5 miles south of HOT. The other aircraft was never sighted by the reporter.
Date: 201908
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 210 Centurion / Turbo Centurion 210C; 210D
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Fuel system malfunction caused forced landing on private property.




Synopsis: Pilot reported fuel system malfunction caused forced landing on private property.
Date: 202012
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other All Flight Phases
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Company Policy; Human Factors
Primary problem: Human Factors

Narrative: On Aircraft X from ZZZ to ZZZ1 while boarding passenger seated in seat XX4 came on that aircraft with his mask below his nose and between his lips. I told that passenger his mask must come over his nose and mouth. He responded 'He will try.' I then offered him a company approved surgical mask that were provided by the company. He responded 'No thanks.' That was the first time of me asking him to put his mask on properly. During my compliant check before doing the safety demo; the mask was down again. I told him once again about the mask. That was the second time. During cabin service the mask was down again and I had to remind him once more. Once cabin service was over and passengers were given time to eat and drink; I then went around to collect trash and he was asleep with his mask down. I called out to him and he opened his eyes and I told him for the third time about his mask. Once we got to the final descent his mask was down and I reminded him once again for the fourth time. Once I told him this time he just looked at me and shook his head. This passenger and his wife; were both sick. They were both coughing without covering their cough. The couple kept coughing during takeoff; throughout the flight and landing. The coughing drew the attention of other passengers to look. People are very scared and when they hear coughing and other passengers not wearing mask properly they worry.  Many verbal warnings were given.




Synopsis: Flight attendant reported two passengers were coughing throughout the flight and not adhering to face mask policy.
Date: 202101
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Physiological - Other; Communication Breakdown; Situational Awareness; Workload
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Passenger X in seat XX3 would not follow crew member instructions to wear her face covering at the appropriate times and manner.




Synopsis: Air Carrier Captain reported a passenger would not comply with face mask policy.
Date: 201210
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Icing
Light: Night
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Aerofoil Ice System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: I am submitting this report as a general safety concern regarding the A300. Landing in IMC; icing conditions prevailed. The windows on the approach were clear with no indication of ice. We joined the localizer and upon selection of flaps 40 the aircraft rolled left to right approximately 2 to 7 degrees momentarily. I looked over my shoulder and noticed a buildup of ice on the left wing. I instructed the flying pilot to increase the airspeed due to the noticeable ice on the wings. After increasing the airspeed the rolling moment stopped and we continued the approach and landed uneventfully. After landing one of the jumpseaters said that we had an accumulation of ice on the wings that he could see. After securing the aircraft I went outside and ice still remained on the outboard part of the horizontal stabilizer. I hope this report helps the Company in address this icing issue with Airbus and improve flight safety for us all.




Synopsis: A300 Captain reports aircraft rolling left to right momentarily during flap extension to 40 degrees and noticing ice build up on the left wing. The flying First Officer is instructed to increase airspeed and a normal landing ensues. Post flight reveals ice on the outboard portion of the horizontal stabilizer.
Date: 201402
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
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Contributing factors: Aircraft; Company Policy; Procedure
Primary problem: Procedure

Narrative: During post flight I noticed that the cargo being off loaded included three boxes that were taped together and had been labeled to contain dry ice. I returned to the flight deck and retrieved the cargo load report which had NO reference to the dry ice that was loaded. I asked the Captain if he had been notified that we had dry ice on board and he said that he had not. The Captain and I then walked to the cargo area together so that he could see the package and noted that the package had a total weight of about 27 pounds with about 2.3 kilograms of dry ice inside the package.




Synopsis: A CRJ First Officer doing a post flight inspection noted cargo labeled to contain dry ice being removed from the cargo pit. No hazmat notification had been provided to the flight crew prior to their just concluded leg.
Date: 201405
Local time of day: 1801-2400
Location: RSW.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: B717 (Formerly MD-95)
Operator: Air Carrier
Operating under: Part 121
Flight phase: Landing
Airspace: Class C RSW
ATC / advisory: Tower RSW
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Airspace Structure
Primary problem: Human Factors

Narrative: Cleared for a visual approach RSW Runway 06 about 10 miles out on a right base. Handed off to RSW Tower and cleared to land. As we approached the outer marker I saw a TCAS target in close proximity at our 10 o'clock position. The target tuned amber and we got an RA to climb. I disconnected the autopilot and started to climb and saw the traffic very close. We continued the approach and landed. No traffic call was issued by RSW Tower. I called Approach Control on the ground and called the Tower Supervisor. VFR aircraft from Page should have instruction to follow the shoreline.




Synopsis: B717 Captain approaching RSW Runway 6; experiences an airborne conflict with a general aviation aircraft departing FMY near DOLPN.
Date: 201205
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Aircraft component: Generator Drive
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During engine start we received an amber IDG 2 CAS message while starting the left engine; the right engine had already been started. I contacted Maintenance Control and we agreed to defer the right IDG and run the APU continuously for the flight. We had plenty of fuel since we only had two passengers and this was a tanker leg; so Dispatch agreed and sent the MEL addition via ACARS. After finishing the write-up and deferral the Maintenance Controller walked me through the M/FC [(Maintenance by Flight Crew)] functions and we then left the gate. A short while after reaching our planned cruise altitude we then received an amber APU OIL PRESS caution message. We referenced the QRH and it instructed us to land at the nearest suitable airport if the APU was essential for flight; which in this case it was.I elected to divert to a nearby regular airport and notified ATC. The First Officer obtained the new clearance and proceeded towards the new destination while I notified the Flight Attendant; passengers; Dispatch via ACARS; and company operations at our diversion airport and requested a GPU at our gate. The balance of the flight was uneventful. Upon landing we were expecting the APU to auto-shutdown after 60 seconds but it continued to run. Once ground power was established I shutdown both engines and the APU.Maintenance arrived shortly thereafter and quickly found the problem of low oil in the APU as well as in the right IDG. They repaired both and cleared the MEL. I contacted Dispatch and informed them that we still had 5;000 pounds of fuel on board and wanted to check if that was enough to go to continue the flight or if we would need to be re-fueled. They determined that we would have enough fuel so we obtained a new release and flight plan and then continued to destination without incident.




Synopsis: With a right IDG defered prior to departure; a CRJ crew intended to run the APU for electrical power redundancy. When they received an APU OIL PRESS warning enroute they diverted for maintenance attention. After servicing the oil quantity in both systems they departed to their original destination.
Date: 201704
Local time of day: 1801-2400
Location: ZZZ.ARTCC, FO
Flight conditions: IMC
Weather elements / visibility: 10
Light: Night
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Descent
Aircraft component: Autopilot
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: With First Officer flying around 17;000 ft while descending into [the airport] we received an IAS comparator. This was followed soon after by the autopilot; auto throttles disconnecting and flight directors disappearing. Shortly after we received Level 2 SEL FLAP LIM OVRD; and SEL ELEV FEEL MANUAL. We [advised ATC] and informed approach control that we were experiencing instrument indication problems. Using the Non-Alert Airspeed Unreliable checklist we continued the descent and navigated using the heading bug until the [ILS] tuned. Shortly after Captain took control of the aircraft. Landing flaps of 35 was selected; but on approach noticed that they had only positioned to 27-28. Flap override was selected to mute a possible TO LOW FLAPS warning. Uneventful landing followed with normal auto brake engagement. Taxi into parking was normal.


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


Synopsis: MD-11 Crew reported multiple equipment failures which they addressed with a checklist to an uneventful landing.
Date: 201412
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain; Snow
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Chart Or Publication; Weather
Primary problem: Weather

Narrative: Landed on Runway in low visibility and with runway markings obscured by snow and blowing snow.  When we sighted the runway about 2 miles out I could not identify any threshold markings or lighting in the snow-covered surface.  Per the instructions on 10-7 I was targeting the area short of the PAPI lights as the aim point (supposed to touch down within the first 1000 feet of the runway).  After landing and taxiing back near the touchdown area the first officer stated that the PAPI lights appeared to possibly be located right near the threshold.  After reaching the hotel I consulted an NOS approach plate for the airport and noted that the location of the PAPI was marked at the threshold (the Jeppesen had no information about the PAPI location).  If it was in fact at this nonstandard location it is possible that we touched down in the overrun.  If the PAPI was at the normal position 1000 feet down the runway then we touched down normally on the runway surface.


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


Synopsis: Because of low visibility; the flight crew used the PAPI as a touchdown aim point. On taxi in; they observed the PAPI to be near the runway threshold; and thought they may have touched down short of the runway.
Date: 201311
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Night
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Squat Switch
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew FLC complied w / Automation / Advisory; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After to gear would not retract in system 2. Switched to system 1 and it retracted but we immediately received faults on ADC2; all pitot heats; autopilot 2 and autothrottles. Unable to clear and after speaking with Maintenance returned [departure airport]. [An] eventful approach and landing. Ground air shift fault?




Synopsis: After the gear would not retract; an A300 crew switched to System 1 which allowed the gear to retract but ADC2; all pilot heaters; autopilot 2 and autothrottles failed possibly the result of the air/ground switch 2 failure.