elihoole/asrs-aviation-reports huggingface dataset:
Date: 201310
Local time of day: 0601-1200
Location: MCI.TRACON, MO
Flight conditions: IMC
Weather elements / visibility: 3
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class B MCI
ATC / advisory: TRACON MCI
Aircraft component: FMS/FMC
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We entered the ILS 19R at MCI into the FMC; and the First Officer briefed arrival and approach. I flowed along on the LEGS pages. We noticed that there was a discontinuity on the missed approach; so he reloaded the approach which solved the problem. While on the approach; we noticed the discontinuity had reappeared. I said that I would give him directions if we needed to go missed and not to follow the LNAV.We went through MCI a second time this day; and still needed to shoot the ILS approach. We went through all our programming and briefing and the same thing occurred the second time too. The LEGS page shows 19R; 2;000 altitude; a 240 heading -----route discontinuity----(INTC); 225 course to RUGBB.




Synopsis: B737-700 Captain reported FMC anomalies involving discontinuities were noted on approach to MCI Runway 19R.
Date: 201706
Local time of day: 0601-1200
Location: BWI.Airport, MD
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B BWI
ATC / advisory: Tower BWI
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown; Time Pressure; Distraction; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: We were about to takeoff on 28; and Dispatch advised us to return to the gate due to a power outage [at destination]. We returned to a gate in BWI; shut one engine down; but waited at least 30 minutes for a Ground Crew to park us. After about 35 minutes; Dispatch advised us that [destination] was open again. We were still waiting to be parked; so we amended our Release for the fuel we burned; ran the numbers for our lighter weight; ran the Before Push and Before Taxi Checklists; and taxied back to Runway 28 for departure. During the initial climb; I noticed that we had departed without arming the autobrakes.We should have run the Before Start Checklist before we restarted the number 2 engine again; due to the fact that we did the after landing flow while we were taxiing back to the gate.




Synopsis: B737 Captain reported taking off without arming the autobrakes.
Date: 201505
Local time of day: 1801-2400
Location: ZHU.ARTCC, TX
Flight conditions: IMC
Light: Daylight
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZHU
ATC / advisory: Center ZHU
Second aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Conflict NMAC; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC Overrode Automation; Flight Crew Overcame Equipment Problem; Flight Crew Took Evasive Action
Contributing factors: Weather; Aircraft
Primary problem: Aircraft

Narrative: While deviating around a line of thunderstorms in IMC conditions; the First Officer and I both heard ATC query a flight to; essentially; increase rate of climb to FL330. We just finished leveling off at FL320. The other aircraft said it would be hard because they bled speed off for some reason I don't recall.The First Officer and I both started scanning the TCAS for the traffic and at that moment we saw the traffic's icon turn yellow indicating an altitude of FL323 and the icon was converging on our path from the right. We then received a climb RA command and I began a commanded RA climb of 700 feet per minute and it dawned on me that is was foolish to climb as the aircraft was 300 feet above me.  I started an immediate descent and went down to FL317. The RA resolved and I returned to FL320. We reported the RA response and the other aircraft reported their RA response.


Second narrative: [Report Narrative Contained No Additional Information.]


Synopsis: An air carrier flight crew was issued an RA climb command while in cruise at FL320 that would have climbed them into their traffic which was 300 feet above them. They began to comply but then descended instead to remain clear of traffic.
Date: 201808
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Aircraft component: Nosewheel Steering
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Troubleshooting
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Around -/+ V1 on takeoff; aircraft pulled hard right; added full left rudder for directional control. After conversing with passenger and SIC (Second in Command) in the interest of safety proceeded to alternate ZZZ1. Wider longer runway with safety personnel and equipment. Made normal landing was uneventful. Passengers were very calm and collected. Complied with all FAR and company procedures. Original destination was ZZZ.


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


Synopsis: Citation Excel flight crew reported directional control issue during take off resulted in a diversion.
Date: 201909
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Aircraft: Citation V/Ultra/Encore (C560)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Fatigue
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Speed All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Work Refused
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Human Factors

Narrative: I'm currently on Day 10+ of a 16-day rotation due to a forced line change from Thursday A Line to Friday B- Line due to bidding as a PIC (Pilot in Command). This past Thursday was the completion of 3 rotations flying with a Line Check Pilot for my upgrade to PIC; culminating in a line check; 135.299; 3 days ago. My 1st day as a PIC was with a First Officer was 2 days ago and took us through 2 time zones; live fuel stop; a Go Around for Helicopters on a runway and a 14+ hour Duty for that 1st day as a PIC. To Central time yesterday and East Coast time today.  Unusual sleep patterns and these time zone changes and long days have contributed to fatigue that we likely experienced with load saturated tasks on approach today into ZZZ; where headings and speed restriction issues occurred; also complicated by distracting loud radio noise on the Approach Frequency. Upon landing; SIC (Second in Command) contacted Flight Control and Chief Pilot to report Fatigue. Repo flight was removed from our schedule. SIC is on Day 10+ of a 12 day rotation for line change as well.Suggestions: If there were somehow a way to avoid Double Rotations when changing lines. Also; avoidance of multiple time zone changes with long Duty Days.




Synopsis: Citation 560XL Captain reported feeling fatigued after a 10 day double rotation; resulting in a series of errors during an approach.
Date: 202001
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
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: 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
Result: General None Reported / Taken
Contributing factors: Manuals; Company Policy; Human Factors
Primary problem: Manuals

Narrative: Passengers and cargo were loaded for normal departure out of ZZZ. After the aft cargo bay was loaded and [clearance] was brought up; I and the First Officer noticed that an electric wheelchair that was loaded into the cargo bay was equipped with a Lithium Ion battery. When I asked the ground crew about this; thinking this was a risk that could lead to a no time threat based on the known threat of a Lithium Ion battery possibly having a thermal runaway. The ground crew leader informed me that it is normal policy to put electric wheelchairs with Lithium Ion batteries into the cargo hold under [the contracting airline's policy]; and he also informed me that the battery was not easily removable; but if I was not comfortable with it they would remove the chair. I elected to tell them to leave it; considering that if the lead knew a policy in place under [the contract airline's] discretion that the proper precautions were taken; and I did not wish to face violating a guest's rights under the Americans With Disabilities Act. Upon reaching stable cruise and completion of the Cruise Checklist; I started searching through our manuals for any guidance on this policy; but was unable to find any. Upon reaching our destination; I was able to find the contract airline's policy on their website.This event came about because it seems that our own information and training isn't keeping up with advancements in accessibility technology.If the contracting Airline does indeed have this policy with us that allows certain Lithium Ion batteries to be loaded into the cargo hold on our aircraft; it should be in our Weight and Balance manual. If this is something our airline is not comfortable with; we need better guidance and documentation that allows us to better accommodate our guests with accessibility needs while also maintaining an operation with the least amount of risk possible.




Synopsis: Air Carrier Captain reported being unable to find guidance in company flight manuals for Hazmat Lithium Ion powered wheelchair transporting procedures.
Date: 202003
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Turbulence; 10
Light: Night
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Military Transport
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Rotorcraft
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict NMAC
Detector: Automation Aircraft RA; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During a Cross Country solo training flight in a Cessna 172SP; I was involved in a situation that resulted in a near mid-air collision with a U.S. Air Force Aircraft Y cargo plane. It should be noted that the bulk of my aviation experience comes from flying helicopters. The majority of my flight experience has occurred in the Northeast region of the United States. On this particular day; just prior to the event in question; I felt very comfortable in the mode of flight I was operating in. I have been attending a full-time part 141 school to 'transition' to fixed wing flying for the past two months. During this time I have logged over 100 hours of flying time in the same type of aircraft I was flying; in the same region the incident occurred. At the time of the incident; I was in the last 20 minutes of an approximately three hour flight. I was flight following with Approach Control when I heard the controller mention my tail number followed by a transmission I did not understand. I asked the controller to 'say again'. The next transmission I heard alerted me to traffic at my 9 o'clock. When I looked out the left window of my aircraft I witnessed an Aircraft Y; less than one mile from me; rapidly descending out of my altitude. I immediately initiated a climb. I informed the controller that the Aircraft Y was passing below me. I then heard the Aircraft Y pilot mention that his RA had alerted him to my position. Had it not been for the quick actions of the pilot of the Aircraft Y; I believe we would have been on a direct collision course with one another. I was complacent in the fact that I expected ATC to give me pertinent advisories; knowing full well that while flying VFR those advisories come on a work-load permitting basis. This situation could have easily ended in disaster had it not been for the last minute advisory I got from ATC; combined with the quick actions of the Aircraft Y pilot. I was not actively scanning my surroundings and I failed to notice the Aircraft Ys ASD-B position on my EFB.




Synopsis: A General Aviation pilot on a solo cross country training flight reported a NMAC.
Date: 201911
Location: ZZZ.Airport, US
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical; Ground Incursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During taxi in after landing. We were inbound on centerline of [alley]. Catering truck was extended past a white line on the ramp as it prepared to back into service the rear door of an aircraft parked at [gate]. I had just transitioned APU onto the bus. Looked out to see we were not going to clear the truck and notified Captain. Brought aircraft to immediate stop.




Synopsis: B737 flight crew reported that a catering truck parked inside the gate safety zone resulted in a ground conflict.
Date: 201603
Local time of day: 1201-1800
Location: ZAB.ARTCC, NM
Flight conditions: VMC
Light: Daylight
Aircraft: Rockwell North American Civil Twin Jet
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I had gone to the cabin to check on our elderly passenger who was traveling alone and has had 2 heart attacks and has a defib/pacemaker implant. While in the back; I noticed we were in a right banking turn so I immediately went back to the cockpit to see what was going on and noticed the autopilot disengaged light was illuminated and asked if we were being vectored. The copilot then realized that we were off course and in a gradual climb. I told him we needed to correct to which he [replied he] was already doing so and I overheard him tell Center that we were correcting. I hopped back in my seat; strapped in; and I took command. Upon discussing what happened; we agreed that if one of us is absent from the cockpit; the Pilot Flying (PF) is responsible for monitoring everything until the other pilot returns. The PF was apparently filling out the engine trend monitoring report and inadvertently tripped the autopilot.




Synopsis: Captain reported the First Officer (FO) allowed the aircraft to deviate from assigned altitude and track while he was out of the cockpit.
Date: 201712
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Elevator Feel System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff; [we] got 'Elev Feel' status message. Consulted manuals then called dispatch and [Maintenance]. [Maintenance] said we needed to return to Departure Airport. [Notified ATC of our predicament]; performed overweight landing. Touchdown normal; had ARFF (Aircraft Rescue and Fire Fighting) standing by to check brakes. ARFF said all brake temperatures normal; taxi to gate.




Synopsis: B767 Pilot reported that they received an 'Elev Feel' message after takeoff. After consulting with maintenance; they returned to the departure airport.
Date: 202111
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine Air Anti-Ice
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Troubleshooting; Communication Breakdown
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Human Factors; Procedure; Aircraft
Primary problem: Aircraft

Narrative: DATE at XA:14 AM the event occurred on the departure on [Runway] XXL at ZZZ airport where the weather was overcast and around 7 degrees Celsius. At about 1;100 feet AGL; we encountered icing conditions with a TAT of around 6C where I selected the engine anti ice on. After about 30 seconds after selecting the engine anti on we noticed the 'eng anti-ice' light illuminated; which indicates a engine core valve has failed to open. We followed the QRH procedure where it told us to avoid icing conditions which we were encountering. At that point we were assigned higher which put us in a layer that keep us out of icing conditions for a period to make a decision to return to ZZZ or continue to destination. With weather over the mid Atlantic and possible icing conditions in view; we decided the best course of action was to get below the cloud layer and return to a long runway at ZZZ. We decided to land overweight giving the runway margin we figured in our 'landing app'. We called company; informed FA; the passengers and informed ATC that we were overweight to [have] emergency vehicles standing by at the end the runway. The landing was made by the First Officer which was smooth and right in touch down zone. We let it roll to the end with min braking to avoid high brake temps. Command One checked the brake temps and followed us to the gate.I would have advised ATC myself; I was under the impression that when ATC asked if we were overweight and need emergency vehicles standing by.  Next time I will transmit the 'pan pan pan ' immediately.




Synopsis: B737-800 Captain reported an air turn back and over weight landing was caused by an engine anti ice valve failing to operate.