elihoole/asrs-aviation-reports huggingface dataset:
Date: 201309
Local time of day: 0601-1200
Location: VVTS.ARTCC, FO
Flight conditions: IMC
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb
ATC / advisory: Center VVTS
Aircraft component: Powerplant Lubrication System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Procedure; Aircraft
Primary problem: Aircraft

Narrative: Number 2 engine oil temp exceeded 162 C (advisory triggered). Aircraft was written up on inbound leg for high oil temp of 162 C. Maintenance had performed service/engine run. Mandatory shut down per QRH is at 177 C or above 162 C for 20 min. [On the next leg] based on the previous write up; the speed of the oil temperature rise and the fact that we were about to be overwater for 2 hours with no fields nearby; we elected to return. Temp peaked at 168 C 9 minutes after exceeding 162 (we were already in the descent). No emergency was declared and there was an uneventful approach and landing. Better Maintenance personnel.




Synopsis: A300 First Officer experiences high engine oil temperature on the inbound leg and the fault is written up in the logbook. Maintenance is performed and the flight departs on the return leg. High oil temperature is again experienced and the crew elects to return to the departure airport.
Date: 201204
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: M-20 R Ovation
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was the FLM in the Tower. It was the last hour of the shift for the crew who was working. Traffic had picked up and we had just changed flows. The Controller working Local was certified through the Tower and training in RADAR; the Controller working Ground was only certified through Ground. Considering the experience level of these two controllers; I was being extremely attentive. The Local Controller approved an approach to an inactive runway; increasing the complexity and his own workload. He was also distracted by a low altitude pipeline aircraft off the departure end on Runway 21. A Mooney was between a half mile and a mile out for Runway 21 and the Local Controller told a B737 to line up and wait on Runway 21. A Controller who was not on position in the back of the cab and I both immediately spoke up and said 'No; no; no!' before the Local Controller had even unkeyed his mike. The Local Controller amended his instruction and a potential catastrophe was averted. There was no loss of separation. The Local Controller stated he was so focused on the utility aircraft that he had forgotten about the Mooney. This event really scared me. The Local Controller has been certified on Local for over a year and is always very conscientious. I was surprised he could have missed this. He has struggled in RADAR training and as his FLM; I try to get him as much quality training time as possible. While he gets his currency time every month; it is often during weekends or slower weekday traffic. I am going to try to ensure that he gets more time working tower positions during busier traffic. We all want developmentals to train as much as possible so they will certify sooner; but it does them a disservice to allow their skills to atrophy and place them in situations where they get overwhelmed. This event also highlighted to me the importance of a strong team and how vital it is for us to look out for each other.




Synopsis: Tower Supervisor described a 'corrected' conflict event unknowingly set up by the Local Controller; but caught by the reporter. The reporter indicated that the minimally experienced Controller was focused on another operation and failed to note the error.
Date: 201404
Local time of day: 0001-0600
Location: CLT.Airport, NC
Light: Night
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Pax Seat
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: We were flying an Airbus 321. Upon arrival; the extra Flight Attendant stated that she believed the aircraft passenger seating in coach class on the right side of the aircraft were incorrectly installed. She stated that the actual locations of the passenger seats interfered with her ability to arm; disarm and potentially operate the 3R emergency exit door; in the event of an actual emergency. I reported this to Maintenance and completed a discrepancy write-up in the aircraft maintenance logbook. Maintenance confirmed the seating was incorrectly installed and removed the aircraft from service. Evidently; the aircraft passenger seats were incorrectly installed [during] heavy maintenance.




Synopsis: A pilot was notified after the flight that a Flight Attendant had noticed that the passenger seat location interfered with the arming and disarming of the emergency exit door. Maintenance personnel confirmed that seats had been incorrectly installed and required repositioning.
Date: 201908
Local time of day: 0601-1200
Location: EWR.Airport, NJ
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Takeoff / Launch
Airspace: Class B EWR
ATC / advisory: Tower EWR
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Human Factors; Environment - Non Weather Related; Aircraft
Primary problem: Aircraft

Narrative: Upon departure from ZZZ; observed small quad-copter type drone colored red and black pass overhead our aircraft while climbing through approximately 900 feet MSL.  Estimated  within 50 feet directly over our departure path.  Reported the sighting immediately to Tower before switching to departure frequency.  Remainder of flight uneventful.




Synopsis: An air carrier pilot reported a NMAC with a drone.
Date: 201509
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Flight phase: Parked
Aircraft component: Hydraulic System Lines; Connectors; Fittings
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural MEL / CDL
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Release Refused / Aircraft Not Accepted
Contributing factors: Incorrect / Not Installed / Unavailable Part; Aircraft; Procedure
Primary problem: Procedure

Narrative: During preflight; First Officer found an approximate 3-4 ft circumference area of oil on the ground around right main landing gear. Oil also filled cement joint crack for 5-6 ft. Found substance leaking from main landing gear actuator at approximately 1 drip per second. Reported to mx and entered discrepancy into logbook. Maintenance pressurized hydraulic system. Took [the logbook] and left.Maintenance applied MEL to gear actuator. After reviewing; MEL; I re-inspected the landing gear drip. Based on my second inspection of the gear and drip; I felt the MEL was inappropriate to the condition of the aircraft. Specifically; the drip per minute appeared to be in excess of the amount allowed by the MEL. The drip rate along with the amount of fluid on the ground gave me cause for concern. The Maintenance person who returned the [logbook] told me that [maintenance control] had made the decision on the MEL not the crew working on the aircraft and that they did not have part to fix the aircraft. The part was in [another airport] and the aircraft was scheduled to have the part replaced when it reached [the other airport] at the end of the day. After hearing this and given; our concerns I refused the aircraft.Maintenance called [Chief Pilot]; who also inspected the aircraft and reviewed the situation with both crewmembers.




Synopsis: A321 Captain reported refusing the aircraft when he determined the hydraulic fluid leak exceeded the allowable under the MEL.
Date: 201905
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Brake System
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; General Evacuated
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: I was performing a post-maintenance flight in an airplane that is new to me. I departed on and entered the right hand traffic pattern. I performed 5 touch and go landings. On my 6th and final landing I tried coming to full stop but the brakes weren't as effective as I was expecting and the airplane rolled into the weeds at the end of the runway. I called the tower frequency to report that my airplane had rolled into the weeds but that I was okay and the airplane was undamaged. I then called my mechanic who came out and helped me push the airplane back onto the paved surface.




Synopsis: Light Sport airport pilot reported a runway excursion due to insufficient braking.
Date: 201301
Local time of day: 0001-0600
Location: IAD.Airport, DC
Aircraft: Dash 8-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower IAD
Reporter organization: Government
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Air Carrier X filed and was issued IAD..COLNS..HVQ..CRW. Preferential route changed it to LDN.J134.COLNS.J6.HVQ. The change was thought to be the old route. The filed route was issued; but the preferential route was not suppressed. The Aircraft got airborne and the Departure Control thought Air Carrier X was issued the preferential route. I realized the error and called Departure Controller to let him know. No separation was lost. The Departure Controller fixed the issue in the air. Recommend following through with any changes that are made for issuing the clearance to the pilot and making any changes in the computer before going on to something else. Also; remember to use strip marking. Strip marking was forgotten here and it could have prevented the situation.




Synopsis: IAD Controller voiced concern regarding the 'lost art' of strip marking providing a recent example of same.
Date: 201401
Local time of day: 1201-1800
Location: MDW.Airport, IL
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E C90
ATC / advisory: TRACON C90
Aircraft component: FMS/FMC
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Human factors: Communication Breakdown; Confusion; Training / Qualification
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Airspace Structure; Human Factors
Primary problem: Ambiguous

Narrative: On departure climbing out of MDW; Departure cleared us direct BACEN. I was the Pilot Not Flying and inserted BEKKI thinking it was what the Controller was saying. The Captain did not catch my mistake and we were handed off to Center. They asked where we are cleared to and I said BACEN and realized my mistake. Then Controller wanted us to go direct BACEN. I am new to MDW flying and that was a lot of the problem. The other issue is BACEN does not look like 'BACON' to me and we had three waypoints in a row that all started with the letter B. It was mainly my lack of experience that caused this deviation and a little miscommunication.




Synopsis: After departing MDW a crew was cleared direct BACEN but heard BEKKI which was inserted in the FMS and being flown to. ATC questioned the track deviation then recleared the flight to BACEN.
Date: 201906
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 100
Light: Daylight
Aircraft: Baron 58/58TC
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Small Aircraft
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: Leaving ZZZ for missed approach and returning for second GPS approach heading approximately 180. The plane was on autopilot and altitude hold. Traffic alert on GN750 indicated traffic 400 above and to pilots left. I pass behind and below aircraft. After passing aircraft; I made a 180 degree turn to the right to intercept the approach. As I was finishing the 180 degree turn I notices the other aircraft had descended into my flight path. I continued my turn to pass behind and under the other aircraft. At this point the other pilot waggled his wings. The pilot then began a climb. I passed under and behind the aircraft. The pilot contacted me on ZZZ UNICOM and accused me of a climbing turn into him.




Synopsis: BE58 pilot reported an NMAC with NORDO pattern traffic.
Date: 202008
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown; Distraction; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: The flight was planned for an on the hour departure.  The flight crew sent an acars requesting a 15 minute early push. The flight cannot arrive more than XX minutes early per management directive and the flight was making XY minutes early enroute. I meant to click on 'Standby' button in alert messenger; but apparently clicked the 'Early departure approved' button by mistake and flight pushed early; giving them an ETA at ZZZ nearly 1 hour early.  Did not catch the problem until I realized that the flight was showing out and off.Was clicking a little too quickly and mouse cursor apparently was just out of place.  Part of the problem was also that my management-dictated COVID-19 mask was causing my prescription glasses to fog; making it harder than usual to see the mouse on the computer screen.




Synopsis: Dispatcher reported erroneously giving permission for a flight to depart early.
Date: 201209
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Air Data Computer
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At approximately 1;500 AGL on departure the right Air Data Computer (ADC) failed and the First Officer had Yellow Altitude and Airspeed flags on his Primary Flight Display (PFD). He selected the left ADC and climb was continued to FL320 as the relief pilots researched the Aircraft Operating Manual and I contacted Dispatch and Maintenance Control for guidance. Maintenance Control advised no corrective procedure was available and I elected to pull and reset the Right ADC Power Circuit Breaker in hopes this might correct the malfunction. The ADC remained inoperative and further investigation revealed two ADC's were required to traverse RVSM airspace. Dispatch coordinated our return with Center and; when clearance was received we dumped fuel on the return. An uneventful diversion was completed.




Synopsis: A long range air carrier flight had to return to their departure airport when a failed ADC and the need to utilize RVSM airspace proved incompatible.
Date: 201402
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Descent
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Spoiler System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown; Fatigue
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Other / Unknown; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft; Human Factors; Weather
Primary problem: Weather

Narrative: Descending for landing after a long duty period; the spoiler handle was harder than normal to pull back with the aircraft taking a slight roll to the right. The period began with two de-icings; one attempted block out with a return to gate; over six hours sitting in the aircraft monitoring ATIS-WX-ATC. The First Officer was pilot flying; he tried it twice; I tried it once to verify. Spoilers were noted to be slightly less on the left wind on the CONFIG page; thus confirming the roll. [We] landed smoothly in light left to right crosswind and the #8 tire failed immediately. [We] taxied slowly to the ramp after advising Maintenance and ATC. The airport sent a vehicle to inspect the runway and taxiway. [We] taxied to the ramp without any pull; dragging; or problem. The amount of slush prior to takeoff; including the taxiways; amounted to water freezing when airborne in both the spoilers and gear. We found out upon landing that ice and slush were the cause of the degraded spoilers. We were within the limits of the Type 4 deicing and left the gear down about 20 seconds after takeoff to aid in removal. Not quite sure if this helped as we were flying into the heavy wind; rain; and snow. We were at the limits of patience; duty; tiredness; and airport closure. Two B-777's were calling it quits and delaying their departures until the morning field opening. The operation was difficult on the Maintenance personnel also. We should have called it quits also and gone to the hotel.




Synopsis: MD11 Captain describes a long duty day caused by two de-icings and maintenance. The flight eventually departs from a slushy runway with snow falling. During descent for landing the spoilers will not deploy symmetrically and the handle is stiff. Upon landing a main gear tire fails immediately. Frozen brakes are suspected.