elihoole/asrs-aviation-reports huggingface dataset:
Date: 201206
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Inflight Shutdown; Flight Crew Landed As Precaution; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was First Officer and pilot flying cruising at FL330. Crew observed high oil temp indication and decreasing oil quantity on Engine #1. Emergency was declared with ATC and we initiated turn to [nearest suitable airport]. Within moments ATC advised that [that airport] was about to 'close down' and we elected to divert and proceed to [another airport] as most suitable. QRH checklists were also initiated which resulted in an in flight shut down of affected engine. Dispatch was notified of situation and intentions initially through ACARs and then [Commercial radio].All pertinent checklists were followed and complied with; all required communication with cabin crew was achieved; and all elements requiring a safe approach and landing were briefed and complied with. Communication with ATC was uninterrupted and precise and Captain made landing without further incident. Clearing runway; communication with local fire chief was established and it was determined that left engine was dripping oil but otherwise aircraft was safe to continue normal taxi to gate. Passengers were then safely deplaned through an available jet bridge and aircraft secured as the situation warranted.


Second narrative: [Narrative #2 contained no additional information.]


Synopsis: MD-83 flight crew reported low oil pressure and quantity and rising oil temperature; so the engine was shut down and a divert accomplished to the nearest suitable airport.
Date: 201606
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: A320
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: Cowling
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Passenger
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Following a normal flaps 1 takeoff and climbing through approximately 5500 feet on departure; we received a call from one of our flight attendants saying that a passenger reported they saw two pieces of something fly off the right side of the aircraft sometime during takeoff.  We asked the flight attendant to further investigate by looking out the window at the right engine and then report back to us.  During this time I told my FO (First Officer) to request a level off while I also slowed the aircraft as not to aggravate any abnormal condition with the engine or airframe.  Also during this time; all engine and other aircraft indications appeared normal in the cockpit.  Shortly thereafter; our flight attendant reported back to us that a portion of the inboard right engine cowling was missing from the aircraft.  I acknowledged this and shortly thereafter had my FO coordinate a return to the airport with ATC.  Also during this unscheduled return; ATC informed us that a portion of our right engine cowling had been found on the departure runway.  I briefed the passengers and flight attendants on our situation and informed them that the aircraft was operating normally and that we would be returning to [departure airport] as a safety measure. My FO and I accomplished all required checklist items and I safely landed and taxied the aircraft to the assigned gate without further incident.


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


Synopsis: A320 flight crew reported returning to departure airport after losing part of the right engine cowling on takeoff.
Date: 202106
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Rudder Pedal
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Confusion; Situational Awareness; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Regained Aircraft Control; Flight Crew Rejected Takeoff; Flight Crew Took Evasive Action; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: I took off Runway XX at ZZZ in a Cessna 172S NAVIII GFC700 airplane and veered off to the left of the runway onto the grassy non-movement area due to a loss of rudder control during the initial acceleration portion of the takeoff. The loss of rudder control was pilot error. The airplane parking brakes were left on. When I realized the loss of rudder authority; the throttle control was brought to idle; and the airplane was subsequently shutdown. Shortly afterwards; ZZZ Tower Control arranged Airport 1 (ARFF) to tow the airplane to maintenance hangar. Maintenance personnel inspected the airplane and did not identify any damages to the airframe or propeller. There were also no damages on the runway or the non-movement area.




Synopsis: C172 student pilot reported failing to release aircraft parking brake on takeoff roll; resulting in loss of rudder pedal control and a runway excursion.
Date: 202007
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: Airliner 99
Mission: Training
Flight phase: Climb
Aircraft component: Attitude Indicator(Gyro/Horizon/ADI)
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Instrument
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Speed All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Student was off on speed and pitch; I thought the student was having issues with pitch had their level reset attitude indicator to see if that began climb again. [It] became obvious after a few minutes their attitude indicator was failing; told Dispatch; looked in MELs; elected to turn back. I took over flying landed; then let the student taxi back to ramp.




Synopsis: C-99 Captain reported an attitude indicator failed midflight resulting in a return to departure airport.
Date: 201508
Local time of day: 1201-1800
Location: LAX.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground LAX
Aircraft component: Nosewheel Steering
Component problem: Failed
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 Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented; General Maintenance Action
Contributing factors: Equipment / Tooling; Human Factors
Primary problem: Equipment / Tooling

Narrative: After pushback; we waved off Ground Crew. We saw the communication bag; tow bar; tug; two personnel and nose gear pin streamer. After completing flow items and the Before Taxi Checklist; we called for taxi. I then realized we had no nose wheel steering control. The tiller would move to the right but there was no left authority control input.We notified ATC and held our position. We contacted Ops and requested that Maintenance assist us. Maintenance personnel arrived and using their headset informed us the nose gear steering pin was still installed. After removal; we continued taxi for departure with no further incident. It turned out that the Ground personnel had removed the pin and streamer; however; the head of the pin broke off during removal. This left the shaft of the pin still inserted in the receptacle. The Ground personnel held in his hand just the 'T' of the pin with the streamer attached. That is what we saw and what the Ground personnel assumed to be a proper removal of the pin. The pin had failed/broken at the head of the pin. We learned of this failure by contacting Maintenance via radio after our departure. No further issues occurred and we continued to destination.




Synopsis: B737 Captain discovered that the nosewheel steering was inoperative after pushback and called Maintenance. Maintenance found that the nosewheel steering lockout pin had sheared off at the head. The push back crew removed only the head and the streamer; but not the shaft.
Date: 201705
Local time of day: 1201-1800
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown; Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
When detected: Pre-flight
Contributing factors: Company Policy; Staffing; Weather
Primary problem: Staffing

Narrative: When I took over the shift; we had multiple weather issues; multiple re-routes and a takeoff weight issue. Everyone was answering everyone else's phones in our quad due to the compressed workload and multiple issues everyone was trying to address. [Later] I sent a message to [management] asking for help but I got no response and no one came down to speak to me about the problems I was having. [Another dispatcher] saw I was having multiple issues and he came over; opened up [another desk] and took 10 of my flights.  When you start to get behind in your releases; everyone starts calling which puts you even further behind. I finally called the Director; told him I had multiple issues and was falling really far behind. I told him I was getting calls from the Captains; Chief Pilots and the Stations. I was not able to get a head of the workload and ATC reroutes. I asked him to start delaying the flights on my desk as I could not get to them in a timely manner. I had a thrust reverser MEL and takeoff weight issues; a departure stop and fuel issues on flights. The Dispatch floor was not adequately staffed for the weather and ATC events that unfolded. Additional desks should have been staffed earlier in the day as the weather and ATC issues started to develop.




Synopsis: Air carrier Dispatcher reported being unable to properly perform his duties due to high workload and no assistance from management.
Date: 201210
Local time of day: 1201-1800
Location: BUR.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
ATC / advisory: Tower BUR
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Situational Awareness; Training / Qualification; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: Other Takeoff Roll
Result: Flight Crew Rejected Takeoff; Flight Crew Returned To Gate; General Maintenance Action; General Release Refused / Aircraft Not Accepted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: As I was given takeoff clearance for Runway 8 at BUR I taxied into position and began adding takeoff power. As I did this I noticed that the right engine did not power up with the left engine and the aircraft momentarily steered slightly right before I corrected by pulling back both throttle quadrants and added rudder to correct for loss of centerline. I then advised Tower of the complication and that I would have to abort the takeoff and return to the ramp. I exited Runway 8 and asked Ground if I may proceed to the runup area before going back to the ramp to investigate the issue more thoroughly. After I assessed the situation at the runup pad I returned to the ramp; shutdown; and called Operations to advise them I would have to down that aircraft and switch to another due to right engine complications. No emergencies were declared and no assistance was needed for this incident. This was a maintenance issue that could not be detected by the pilot.




Synopsis: A small cargo aircraft pilot rejected the takeoff at BUR because the right turboprop did not spool evenly with the left and so returned to the gate for another aircraft.
Date: 201701
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Icing; Snow; Windshear; 10
Light: Daylight
Aircraft: Caravan Undifferentiated
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Powerplant Fire/Overheat Warning
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On the downwind portion of the arrival; in preparation for the ILS; we were cleared to begin a descent from 6;000 ft to 4;000 ft MSL. The cloud tops were approximately 5;500 ft. As we began the descent; I retarded the throttle slightly and pushed the nose over. At the moment of throttle reduction; a considerable rollback of power was noted. Additionally; at the same moment; the engine fire warning light illuminated and the warning horn also went off. The warning light illumination and horn sounding lasted for an approximately 2-3 seconds. The power returned to the power setting I selected seconds after the occurrence. Seconds later; the engine fire warning light illuminated again; along with the warning horn; for an additional 2-3 seconds. During the duration of the event; all engine instruments remained within safe limits. Despite this; we did not want to risk the lives of our passengers or ourselves by continuing the flight longer than necessary. Given the portion of the arrival we were on; we knew we would continue the flight for 10-15 NM prior to receiving a vector inbound to intercept the ILS. With this in mind and the seriousness of the possibility of an engine fire; we [advised ATC]; noted fuel on board; and souls on board. We immediately received a vector to turn left to 360 degrees and a further descent down to 2;500 ft. After a second vector to turn 330 degrees; I intercepted the localizer while continuing the descent. As we neared the airport I intercepted the glideslope and successfully completed the ILS. No engine fire was present upon landing; all engine instruments remained within safe limits.




Synopsis: Cessna 208 First Officer reported receiving an engine fire warning on approach; but no evidence of fire was found after landing.
Date: 201305
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Workload
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; Flight Crew FLC complied w / Automation / Advisory; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While flying at cruise we noticed that the oil temperature had risen into the amber range and was continuing to rise. As flying pilot I took the radios and the aircraft while the Captain took out the QRH. The procedure directed us to bring back the power on the affected engine to see if it would reduce the oil temperature: it did not. The procedure directed us to shut down the affected engine. We declared an emergency to ATC; started diverting to a nearby airport; contacted the company; and briefed the flight attendants. We landed safely. We had the emergency vehicles that were standing by verify that everything looked OK on the outside of the aircraft; they said it did. We taxied into the gate and deplaned.




Synopsis: An ERJ-170 engine oil temperature was detected in the amber range and after completing the QRH the temperature remained high so the engine was shutdown; an emergency declared and the flight diverted to a nearby airport.
Date: 201208
Local time of day: 0601-1200
Location: HWD.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Challenger 300
Operator: Fractional
Operating under: Part 91
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground HWD
Reporter organization: Fractional
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: We were given clearance to taxi to Runway 28L at HWD via Taxiway A and A1. Approaching the end of the taxiway a sign to left regarding noise abatement procedures caught my attention. With the layout of the taxiway paralleling the runway; and runup area to the left I did not notice the hold short line. I passed the hold short line; by my estimate; by a few feet with the nose of the plane. Upon noticing my error I contacted Tower and told them what happened. I was given instructions to taxi onto the runway and turn left on Taxiway D; left on Z and hold short. We complied with these instructions. Do not allow distractions such as a sign for noise abatement located near hold short lines to take your attention off the primary duty of taxiing the airplane.




Synopsis: CL300 pilot reports crossing the hold line for Runway 28L on Taxiway A while distracted by attention to a noise abatement sign in the same area.
Date: 201405
Local time of day: 1201-1800
Location: 10D.Airport, MN
Flight conditions: VMC
Weather elements / visibility: 12
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G 10D
ATC / advisory: CTAF 10D
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Ground Personnel
Result: Aircraft Equipment Problem Dissipated; Flight Crew Landed As Precaution
Contributing factors: Aircraft; Procedure; Airport; Human Factors
Primary problem: Ambiguous

Narrative: I was on a personal flight in the vicinity of 10D (Winsted MN). I was experiencing light engine roughness. I noticed another aircraft in the pattern at 10D and contacted him on CTAF. I asked him the condition of the runway after recognizing that there was no indication that the runway was closed. He said it was fine and that he was using it for touch and go's. After determining that a safe landing could be made; I chose to land to troubleshoot my problem. When I reached the apron; I was approached by a male in a vehicle; who stated that the runway was closed and that he didn't need to mark the runway as closed with a yellow X. [Since] I didn't plan on landing at 10D; I did not check the NOTAM's. While I was at Winsted airport; there were four other aircraft using the runway. After doing a thorough inspection and run-up; I determined that the engine was running fine. If 10D runway was clearly marked as a closed runway; I would not have landed.




Synopsis: General Aviation pilot reports landing at Winsted Airport after noting some engine roughness. Upon reaching the apron he is approached by a vehicle and the driver informs that the airport is closed. Aircraft were in the pattern both before and after the incident with no mention of the airport being closed on the CTAF. NOTAM's for Winsted were not checked prior to flight due to no intention to land there.