elihoole/asrs-aviation-reports huggingface dataset:
Date: 201210
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Dash 8-200
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Fuel Booster Pump
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Commercial
Human factors: Confusion
Second reporter function: Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff I accomplished the climb checklist; we noticed that the #1 Aux pump light didn't extinguish. I cycled the #1 Aux pump switch on and off to try and get the problem resolved; we were unable to get the light to extinguish. I notified ATC and contacted Company Operations to notify them of the issue. Shortly after we noticed that we had significantly less fuel on the #1 main tank; and it was dropping rapidly. The Captain declared an emergency with ATC and we returned. When time permitted I advised the Flight Attendant and passengers of the situation at hand and that we were returning. During the flight; after we had declared an emergency; the #1 Aux pump light went out and it appeared that we had stopped losing fuel.


Second narrative: After takeoff the First Officer accomplished the climb checklist; we noticed that the #1 Aux pump light didn't extinguish. We cycled the #1 Aux pump switch on and off to try and get the problem resolved; we were unable to get the light to extinguish. I asked the First Officer to notify ATC and contact Company Operations to notify them of the issue. Shortly after we noticed that we had significantly less fuel on the #1 main tank; and it was dropping rapidly. I declared an emergency with ATC and we returned. When time permitted the First Officer advised the Flight Attendant and passengers of the situation at hand and that we were returning. During the flight; after we had declared an emergency; the #1 Aux pump light went out and it appeared that we had stopped losing fuel.

Second callback: Maintenance could find no defects and believes the missing fuel was transferred to the right tank. The reporter believes that the fuel difference between departure and arrival was significantly more than could be accounted for by the engines. No leak could be found and the Aux pump appeared to operate normally.

Synopsis: DHC8-200 flight crew note the failure of the number one Aux fuel pump to turn off after takeoff when the switch is selected off. Shortly thereafter fuel is noted to be disappearing from the number one main fuel tank. An emergency is declared and the flight returns to departure airport. During approach the Aux pump light went out and the tank appeared to stop loosing fuel.
Date: 201904
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 6
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Approach; Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness; Time Pressure
Anomaly: Conflict NMAC
Detector: Automation Air Traffic Control; Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Airspace Structure
Primary problem: Ambiguous

Narrative: In descent for visual to ZZZ on IFR flight plan from 3;000 feet. ATC cleared for visual and reported traffic. Did not see traffic until it approached from my nine o'clock; passed under me 250 feet below. [There were] 3 different radio frequencies in use. Aircraft departing ZZZ use 122.9 then switch to 132.775 until clear of [TFR]. IFR traffic use either 124.55 or 119.7 until cleared for local frequency 122.9. Other aircraft would have departed ZZZ on [a southeast] heading then turn east in climb towards my position. I had no time for evasive action once I spotted other aircraft. I had lights on and wing and tail strobes flashing.




Synopsis: PA28 pilot reported an NMAC with traffic that ATC had reported.
Date: 201307
Location: ZDC.ARTCC, VA
Flight conditions: VMC
Weather elements / visibility: Turbulence
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; Flight Crew Returned To Clearance
Contributing factors: Weather
Primary problem: Weather

Narrative: Departed holding at FAK at Bingo fuel to divert to alternate. A few minutes out of FAK with seat belt sign on at 39;000 FT encountered severe turbulence; aircraft lost 2;000 FT; stick shaker warning; [and] bank angle warning. Pilot flying took control turned autopilot off and climbed back to 39;000 FT. We asked flight attendants to check for injuries and they reported back there were no injuries. We made a report to ATC there were no injuries. Captain made a log book entry for severe turbulence.




Synopsis: B737 First Officer reported a severe turbulence encounter at FL390 in the area of FAK that resulted in altitude loss and enough roll to trigger the bank angle alert.
Date: 202106
Local time of day: 1201-1800
Location: ZZZZ.Tower, FO
Aircraft: Medium Transport
Operator: Other unknown
Operating under: Other unknown
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Aircraft component: Tires
Component problem: Failed
Reporter organization: Other unknown
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Time Pressure; Training / Qualification; Workload
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: Other takeoff roll
Result: Aircraft Aircraft Damaged; Flight Crew Rejected Takeoff
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: At approximately 130 knots I saw a flock of seagulls coming from my peripheral right side and they started impacting the aircraft with multiple strikes. The Captain was diligent and assertive to abort the aircraft at this time and we came to a complete stop with auto-brakes; spoilers and reversers. I notified the Tower of the abort and requested the AARF and made all the appropriate call outs (spoilers; 80; 60) to back the Captain up on the abort. Once stopped the Captain made the PA 'remain seated x3' and I rolled the flaps to 40 once we verified no doors were open. We held position to run the brake cooling chart and determined we needed one hour. We then had the AARF follow us to the ramp as well to be sure no personnel approached the aircraft. Once parked at the gate; we requested chocks to be inserted on the nose wheel so that we may release the brake pedal pressure as setting the parking brake was not an option. When the AARF confirmed it was safe to have the jet-bridge brought to the aircraft we did so and AARF remained ever ready throughout the entire process. Once the brake cooling was confirmed complete; the Captain; the mechanic and I inspected the tires to find #2 tire flat with fuse plug melted and #3 tire scalloped badly. Both would need replacement. No other damage identified. Too many birds on the airport property that were not easily seen. Adding an air cannon to the airport property to scare off the birds for arriving and departing aircraft.




Synopsis: Non-flying pilot reported an aborted takeoff after encountering birds.
Date: 201304
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Elevator
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were climbing through 6;000 FT and got the elevator split caution message. We ran the QRH and it said to land at nearest airport [so] we chose to go back to [departure airport]. We declared an emergency and landed.


Second narrative: [Narrative 2 had no additional information.]


Synopsis: CRJ-700 flight crew reported EICAS message 'Elevator Split' in climb. QRH directed landing at nearest suitable airport; so they returned to departure airport.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Wind
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Nosewheel Steering
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
Result: Flight Crew Rejected Takeoff; Flight Crew Returned To Gate
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During initial takeoff roll; at takeoff thrust setting and less than 30 kts; aircraft began uncommanded hard left turn. Initiated slow speed reject; tried to counter with full right rudder and full right nose wheel steering. Tiller was binding; only 10 degrees of travel available as if fighting left tiller inputs. Continued manual braking to a full stop with the aircraft nose close to 45 degrees left of centerline with the aircraft fully blocking taxiway. We informed Tower of the rejected takeoff and that we required a tow back to the ramp. Suspected nose wheel steering malfunction




Synopsis: B777 Captain reported rejecting the takeoff and returning to the gate when the aircraft initiated a hard left turn early in the takeoff roll.
Date: 201910
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 190/195 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Cruise
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: APU
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [Flight] reported an odor in both the cabin and flight deck with the APU on climbout. Odor stopped after APU shut off. PIC (Pilot in Command) advises flight will continue to destination. [Did not identify as an] emergency. Dispatch advised all company entities as required including Maintenance Control. Phone call from a different Maintenance Controller regarding flight; [who] demands that the Dispatcher immediately advise the crew that they must fill out the smoke report. I advise Maintenance Control that the aircraft is on arrival; is already a flight with a heavy workload and that I would ACARS the crew regarding smoke report once aircraft had landed. Maintenance Controller became very belligerent; demanding again that I immediately ACARS the crew to fill out the smoke report. I waited until flight had landed; and then advised crew of the need to fill out a report.Maintenance Control apparently believes that it has operational control of all the aircraft being operated by Company. Further; he seems to believe that he can order any dispatcher to take any action he deems necessary at any time. This flight was quite possibly in a sterile phase of flight; with previously mentioned mechanical problems; operating within a turbulence SIGMET that covered a large part of the [AREA]. Maintenance Control could hear none of this; he demanded that the dispatcher immediately tell the crew to fill out a report that could obviously wait. In this instance; Maintenance Control was talking to a Dispatcher with considerable experience. I know that no maintenance entity can assume operational control of any flight; or order any dispatcher to take any action. Maintenance Control needs to be made aware of this before he tries to coerce a dispatcher with less experience or understanding of operational control to take unsafe or unwarranted action. My hope is that Maintenance Control is advised of the limitations of his position in a timely manner.




Synopsis: Dispatcher reported a communication breakdown between Dispatcher and Maintenance Control regarding the urgency of completing a 'smoke report.' Flight continued to an uneventful landing.
Date: 201706
Local time of day: 1201-1800
Location: ZDV.ARTCC, CO
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZDV
ATC / advisory: Center ZDV
Aircraft component: Cockpit Window
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 Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At cruise altitude Captains front window cracked with a loud sound. Crack had multiple fingers and covered about 80% of the window. I [advised ATC] and requested immediate descent and return to KDEN. Pressurization system showed normal indications the entire flight. We accomplished Window Heat ecam and Cracked Window checklist in the QRH. I informed the flight attendants and passengers of the situation and advised it would be a normal approach and landing. Captain's visibility was impaired so I gave controls to first officer and he performed the landing.


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


Synopsis: A319 crew reported that the Captain's front window cracked at cruise altitude. The crew returned to the departure airport.
Date: 201205
Location: CZQX.ARTCC, FO
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight phase: Cruise
ATC / advisory: Center CZQX
Aircraft component: INS / IRS / IRU
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: While attempting to adjust volume of Captain's overhead speaker; I inadvertently turned off the #1 IRU. This occurred at about N43.00.0; W40.00.0. the middle crossing of the North Atlantic. Switched control to #2 autopilot ensured that FMS mode was NAV continued to destination. In my opinion; the current location of the Captain's overhead speaker is poor. Due to the HUD (Heads Up Display) installation; the speaker is blocked by the HUD projector and flood light. It is hard for the captain to hear and too loud for the First Officer. It is also very easy (as I have just demonstrated) to mistake the IRS switches for the speaker volume due to their proximity and that they are partially obscured by the redesign of the overhead panel. In the future I will positively identify the volume knob.




Synopsis: An MD11 Captain inadvertently turned off the number one IRU while attempting to adjust his speaker volume.
Date: 201306
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Light: Night
Aircraft: MD-82
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: Pressurization Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Distraction; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Lost cabin pressurization; Cabin Altitude Warning [we] performed red block items. Immediately regained cabin pressurization with Manual Control. [We] descended from FL330; while the First Officer read the QRH checklist. [We] stopped at FL240 as First Officer had cabin pressure stable with manual control. [We] talked to flight attendants and Dispatch based on information elected to divert.




Synopsis: An MD82's AUTO Cabin Pressure Controller failed at FL330; flight crew declared an emergency and while descending the First Officer stabilized the cabin in Manual Control. After leveling at FL240 the flight diverted to a nearby airport.
Date: 201404
Local time of day: 1801-2400
Location: ZMP.ARTCC, MN
Aircraft: UAV - Unpiloted Aerial Vehicle
Operating under: Part 91
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZMP
ATC / advisory: Center ZMP
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft 1 was a UAV and was cleared to delay in the A4 airspace from FL500-590. I observed Aircraft 1 maneuvering close to the edge of the boundary for some time. I continued my scan and clearances for other aircraft. When I scanned back to Aircraft 1; it was still close to the boundary. As I watched; it got close enough to the edge of the airspace that I alerted the Controller in the adjacent sector; the A4 boundary is the same as the sector boundary. I told the Controller I didn't think Aircraft 1 would be able to turn fast enough to stay in the airspace; and he agreed and said he would block for the aircraft. I waited until Aircraft 1 was about 5 miles outside of the airspace; watching to make sure it turned back but it did not. I called Aircraft 1 and advised him that I was showing him outside the confines of the airspace he was cleared into and asked him to say his intentions. Aircraft 1 answered that he had meant to get clearance into the Tiger North and South airspaces for his return to base; and apologized for the mistake. I coordinated the Tiger airspaces with the next sector over; and then got a D-Side to help with the rest of the coordination for Aircraft 1 and the other traffic in my sector. I don't believe that UAV aircraft are safe enough to put in the mix of regular air traffic. I don't think the pilots of these aircraft understand well enough how they affect our operations. I've had a couple UAV's deviate from their clearances with no communication at all; and showing a lack of knowledge about the National Airspace System and how control instructions and communication work. I think there needs to be more training for everyone involved with the UAV flights. I have been told that they want to hire UAV pilots that do not have regular pilot's licenses; and I think that will cause even more problems than what we have now.




Synopsis: ZMP Controller reports a UAV he is controlling flying out of its designated airspace. When the UAV pilot is contacted he states he meant to get a clearance but forgot.
Date: 201605
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: 12
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class A ZZZ
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification
Anomaly: Aircraft Equipment Problem Less Severe; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft TA; Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Flying a cross country solo student training flight from. While checking weather at the destination; I selected the Comm2 function on the G1000 and didn't realize that I'd turned off the Comm1 radio where I had been monitoring Flight Following. TCAS activated with a warning of traffic and I observed [another aircraft] cross from my right to left approximately 100 ft above my altitude. I was wondering why that traffic hadn't been called out to me when I realized that my Comm1 radio had been turned off. Approach contacted me and said they'd been trying to contact me for the last 20 miles. Obviously a situation where my attention to the radios needs to be improved.




Synopsis: Student pilot on cross country flight temporarily lost contact with ATC.