elihoole/asrs-aviation-reports huggingface dataset:
Date: 201910
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
Aircraft component: FCC (Flight Control Computer)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Conflict Ground Conflict; Less Severe; Ground Event / Encounter Aircraft; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew FLC Overrode Automation
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: During approach for landing and fully established on the ILS Runway XXR at ZZZ. An A320 was given clearance to cross the landing runway from right to left when I was approximately 900 ft. AGL. Crossing aircraft was slow to cross and cleared the landing runway when I was 100-200 ft. AGL. During flare with thrust levers at idle the aircraft rolled uncommanded to the left. I countered the roll with right aileron correction and a balloon ensued. I chose to go around at that point; but due to energy state; engine spool up time and ground proximity the main landing gear touched down before becoming airborne again. Almost immediately after becoming airborne we got master caution alerts and ECAM advisories of flight control malfunctions. Being the Pilot Flying I maintained control and asked what was going on. FO (First Officer) informed me that the autopilot was inoperative and he believed us to be in Alternate Law. We cleaned up the aircraft and both verified the ailerons were inoperative on the F/CTL page and roll control was available via spoilers. The aircraft had reverted to Alternate Law and was verifiable by indications on the PFD.I gave FO the responsibility of flying the aircraft and ATC as I referred to QRH pg 62 F/CTL L(R) AIL FAULT. The procedure simply states that if both ailerons were deflected we would use more fuel. I did a landing assessment with our current state and verified we needed approximately 5700 ft. of runway. I [Requested Priority Handling] and since I had no idea why we were in Alternate Law; I felt the safest course of action was to return ASAP to ZZZ for a landing as opposed to trying a computer reset. I had full roll and pitch authority and didn't know what would happen if I tried to reset the computer; nor did I know which ELAC was inoperative. A normal approach and landing was made to Runway XXL. No limitations were exceeded. I attribute the whole scenario to the slowly crossing aircraft. I have never had an uncommanded roll in the flare during landing. From now on if a crossing aircraft has not cleared the landing runway by the time I get to 400 ft. AGL I will initiate a go around.




Synopsis: A321 Captain reported a go around after an uncommanded roll at 100 ft. AGL and loss of an ELAC.
Date: 201603
Local time of day: 0601-1200
Location: ZZZ.Tower, US
Flight conditions: IMC
Weather elements / visibility: Fog; .5
Aircraft: Cessna 425/441 Conquest I/Conquest II
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Excursion Runway; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: Weather at destination was forecast to be VFR at arrival time and everything except destination was improving. Flew the ILS 28R approach to minimums and executed the missed approach and climbed on top fog deck which was about 300-400 feet thick. Entered a hold and watched the fog move slowly out of the area. Requested the RNAV 28R approach and this time at minimums saw a portion of the runway and executed the missed approach and held again. A few minutes later the fog appeared to be thinning and requested the RNAV 28R approach again. I entered the top of the fog layer at about 800 feet MSL and at minimums I looked up and saw the runway environment in sight and continued my descent. The last time I looked at the airspeed indicator I was at VREF and at about 50 feet I reduced power to flight idle. In the flare the aircraft floated and I forced it on the runway in a level attitude; touching down in the first one third of the runway. Shortly after applying brakes and reverse pitch I realized there was not much runway left and I used maximum braking and reverse pitch. As I neared the end I was slowing considerably but did not think I could stop before the end of the runway. I quickly considered the grass overrun at the end and entered it at about 20 knots; reducing my reverse to flight idle. I executed a 180 turn on the smooth overrun and reentered the hard surface runway without any damage to aircraft or property. After arriving at the FBO I carefully inspected the aircraft and found no damage.After replaying everything over I realized that I had looked at the runway length; on the approach plate and had overlooked the displaced threshold; making the runway long and obviously even less from where the glide path intersects the runway. Five minutes after my landing the fog was dissipating quickly and had I waited I could probably have landed visually.




Synopsis: The pilot of a C-441 reported a runway overrun after an instrument approach to minimums and a slightly long landing. The useful runway length was reported to have been overlooked.
Date: 201511
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Challenger 605
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Powerplant Fire/Overheat Warning
Reporter organization: Corporate
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Engineer; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing through the FL280 we received a CAS message indicating we had a right engine fire. We stopped our climb and [advised ATC] and performed our appropriate checklist which lead to an engine shut down. We may have started our descent before we had ATC clearance. On single engine we were not going to be able to hold our altitude. We returned to [departure airport] without incident.




Synopsis: CL605 Captain reported returning to departure airport after shutting down the right engine because of a fire indication.
Date: 201511
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
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 System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Cruising at FL370; the aircraft lost cabin pressurization. We complied with all our immediate actions items; QRC; and QRH Checklists. We started to initiate an emergency descent to 10;000 feet MSL because we were unable to control the cabin. [Advised] Center. We advised Dispatch of our situation. We had enough fuel onboard to continue to [destination]. As we leveled off at 10;000 feet MSL; we started to get a burning smell in the cabin and cockpit; so we then advised Center we needed to divert immediately. We were right on top of [a suitable alternate]. We advised Dispatch now we are diverting there due to the burning smell. We amended our Release; did all our checklist and landing data. We landed within eight minutes. I made the announcement to the Flight Attendant and passengers to remain seated and not to evacuate. Fire rescue was waiting for us. After landing; we had fire rescue access the aircraft. After that we taxied to the terminal and parked at a gate to offload our passengers. First Officer and I worked very well together. He flew and talked to ATC while I coordinated everything else. We were able to do all our checklists in that short time.




Synopsis: B737-700 Captain reported diverting after experiencing loss of cabin pressure and noticing a burning smell.
Date: 202103
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Fuel Storage System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Inflight Shutdown; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Shortly after takeoff; we noticed a fuel imbalance of about 1;200 pounds with the right tank showing a lower quantity. As we were monitoring the fuel gauges; Flight Attendant called to advise a passenger noticed fluid coming out of the right wing after takeoff. Captain was able to balance the fuel.After established in cruise for about 10 min; started to notice another fuel imbalance in progress. Captain ran FUEL LEAK QRH and noted time and fuel quantities. Got to a fuel imbalance of 650 pounds within 20 min.At this point Captain and I concurred that it looked like we had a fuel leak. Advised ATC of the situation and requested to divert to ZZZ1. Continued and finished QRH checklist. Performed an engine shutdown followed by a single engine landing.




Synopsis: B737 flight crew reported a fuel leak required an in flight shut down of an engine and a diversion.
Date: 201511
Location: ZZZZ.Airport, FO
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Other Preflight Planning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness; Workload
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy
Primary problem: Company Policy

Narrative: The so-called flight planning area in ZZZZ is unsuitable. This is my 4th report on this station in the last year. The room is 9x9 room on the ramp level that is used by the ramp personnel to load the baggage scanner info; etc. There is a desk with a company computer; a printer and a phone. The phone to call dispatch does not go to dispatch. You have to call the number for maintenance control and get transferred over. There is one chair and not enough room for laying out a plotting chart; marking up flight plans; etc. The very nice (did I mention very nice?!?) Foreign Airline agents print off the paperwork for us and hand it to us as we walk down the jetway. If we were to go to the planning room we would need a ramp agent to come to the airplane and escort us down to the room and unlock the door. Most of the crews don't do this so most of the crews wind up taking what the dispatcher plans and probably never calling for a dispatcher briefing. Flight planning in the cockpit is not the best; safest practice - way too many distractions and not enough room.




Synopsis: B767 Captain described the conditions under which flight planning is completed at a foreign airport with no Company Operations in a small room with inadequate communications.
Date: 201811
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-44 Seminole/Turbo Seminole
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Gear Up Landing
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: I was piloting a PA44 on a training flight with a student. We had just completed a two hour flight which originated from ZZZ with training north of ZZZ and landings at ZZZ1. We then returned to ZZZ for a full stop landing. I reported ten miles to the north and was instructed to report a right base for Runway 24. Upon reaching a 2 mile right base; I performed the landing checklist; moving the landing gear position handle into the down position and then proceeded to add flaps through the ranges of 10 degrees; 25 degrees and then full to 40 degrees. After crossing the threshold; I retarded the throttles to idle. As we continued our descent; I began the transition and landing phase. It was at this point that we made contact with Runway 24 sliding to a stop on the belly of the aircraft. During my final approach; and while I retarded the throttles to idle; there was no audible warnings that the landing gear was not in the down position. We notified the Tower of our situation and exited the aircraft without injury.




Synopsis: PA-44 Flight Instructor reported a gear up landing.
Date: 202104
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Autopilot
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Commercial
Human factors: Confusion; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: After being cleared for the ILS XX in ZZZ; I initiated a descent to 1;600 ft. and began slowing from 250 kts. On the left downwind just past ZZZZZ the aircraft made an unprompted right turn away from its present course. The aircraft was in heading mode and I (FO) attempted to correct the course deviation with the heading bug but the autopilot was unresponsive. The GPWS went off with a caution message due to the terrain south of the field. The CA then took manual control and initiated a climb away from the terrain and back on an intercept course. The GPWS and Radar Altimeter (RA) sounded another caution on the intercept back to the ILS even though there was no terrain present. The CA initiated another climb and then resumed course. He asked me to configure the aircraft for the approach and then handed back controls for me. The approach was then completed in a stabilized and safe manner with no further incident. The initial error was a malfunction with the aircraft turning right unprompted but the human error was the PF (FO) not disengaging the autopilot immediately and instead allowing the situation to degrade into a GPWS caution. Much of the situation could have been avoided if the autopilot was disengaged and the approach hand-flown instead of a reliance on automation. The terrain was briefed initially but I lost situational awareness of its location on the downwind. The mistake won't be made again.




Synopsis: CRJ900 First Officer reported receiving a GPWS alert while on a downwind vector for an ILS approach.
Date: 201707
Local time of day: 0601-1200
Location: ZID.ARTCC, IN
Light: Daylight
Aircraft: 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 ZID
ATC / advisory: Center ZID
Second aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Air Traffic Control; Automation Aircraft RA
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was leveled at FL300 direct VHP after reroute for weather. Aircraft Y was turning to FLM after EMEGE at FL290 looking for higher. Aircraft Y checks on and I immediately climbed to FL310 missing a keystroke for the interim altitude (which would've resulted in an immediate conflict alert). After Mode C showed FL292; conflict alert goes off to which I responded with a vector of 40 degrees left on both aircraft. Right after vectors were issued; pilots started responding to RAs. Traffic was never called since I was focused on the situation analyzing how to avoid it from becoming worse than what it was. After FALCON review the closest point was 2.55 miles and 800 ft. This was all a personal issue. Traffic was overlooked and keyboard entry for interim altitude was missed which would've resulted in immediate conflict alert. This would've given me time to react and stop Aircraft Y at FL290.




Synopsis: ZID Center Controller reported climbing an aircraft into conflict with another enroute aircraft.
Date: 202008
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Distraction
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Prior to pushback; after 'all passengers boarded' PA had been done; I did my briefing to the passengers who had been seated there. At this time seat XX2 had still been unoccupied. On my way forward; I secured the forward portion of the aircraft; where I had 2 passengers in seats Y1 and Y3 with all 3 tray tables down and all their carry-on items in the middle seat. I asked them to stow their items and continued forward. In the time that I made it forward; 3 more passengers boarded. First a gentleman; then 2 others that were traveling together. Without stepping in front of the first gentleman I acknowledged to him that there were still empty rows left in the back of the aircraft. I said the same thing to the two guys (traveling together). I saw the 2 guys make it to the back; but did notice the first gentleman sit down. During the demo; on my first walk-through; I had to stop at row X for the second time to address the carry-on and tray tables; although I would have most likely noticed the gentleman at this time; I did not. I knew we had been told we were on a 'short taxi' so there was a time constraint already. During my oxygen demo; I once again had to address row X; as they still had not moved their carry-on and now were not wearing their facial coverings. Again; I did not notice the gentleman.We quickly got up after 10;000 feet; I went to the back to get the snacks and this is when I realized he had not been sitting there when I briefed initially. I distributed snacks and then went to the gentleman who was sitting in seat XX3 and his wife who had moved to YY2 after he boarded. I gave him a briefing at that time.




Synopsis: Flight Attendant reported not briefing an exit row passenger due to the late arrival of the passenger.