elihoole/asrs-aviation-reports huggingface dataset:
Date: 201911
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
Aircraft component: Horizontal Stabilizer Control
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Conducted operational check flight after maintenance repairs were made for previous pitch trim runaway event. Prior to the flight the Captain and I confirmed with maintenance about what was fixed and the probability of it happening again. They said they were certain that the problem had been fixed but just wanted to ensure by conducting the flight. Prior to the flight the Captain and I discussed call outs and actions should we have another trim runaway. While conducting the preflight checks per our SOP we checked all trim indications and ensured that they cut out after the appropriate time. Taxi out and takeoff were normal. It was about 400 ft. off the ground the Captain commanded a normal trim down however he realized quickly that the control column was harder and harder to push in order to maintain the takeoff pitch shown on the Flight Director. Captain immediately called for the Pitch Trim Runaway and we both performed the memory items; and ran the QRC and the QRH. Shortly after we were able to regain the pitch control using system 2 and [advised ATC] for a return to field. I flew the airplane to a landing due to my side having the authority.




Synopsis: E175 First Officer reported that a pitch trim runaway resulted in a return to the departure airport.
Date: 201901
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
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)
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors
Primary problem: Human Factors

Narrative: Flight to Nashville. Dispatch Release had a note (to the effect) alternate added due to possible rain at destination Nashville. We were in an -800. Dispatch planned the fuel with approximately 13;000 pounds of tanker fuel. Our arrival fuel was planned at approximately 21;500. Although we were not close to Max Landing Weight; the arrival fuel got my attention because this is probably the most fuel I have ever seen (tankering/landing with) in my tenure at Company.Thinking through this; our crew discussed that the fuel load seemed a bit odd. Nashville airport doesn't have the longest runways (02s and 20s); plus the note about the rain. In an attempt to ensure we were keeping the priorities in the proper order; I decided to call Dispatch. Upon reaching our Dispatcher I explained the reason for the call. The release had a comment about alternate added due to possible rain at the destination. He said that it wasn't going to start raining until after our arrival (this struck me as somewhat dismissive because we all know the forecast can be wrong). So I explained to him that it looked odd having that much tanker fuel with possible rain. He told me that 'All the 'T's had been crossed and all the 'I's had been dotted; everything has been done the right way; routine... etc.' I said 'OK; but it just seems a little abnormal.' He said 'Not to be snarky; but I Dispatch more flights in a week than you fly in a year.' I thought to myself 'Wow...how many landings does this guy have in a heavy -800 on a short-ish wet runway?' Instead I said something to the effect that 'Dispatch doesn't always do the smart thing (none of us do). No one is infallible.' At that point the Dispatcher became really annoyed; asked me if I wanted to get the Chief Pilot on call involved. I declined and said that I was calling to see if it would be raining in Nashville for our arrival.We all make mistakes. We are all on the same team. Feedback helps us discover our mistakes. Arrogance does not accept feedback. Help each other out by listening and being humble.




Synopsis: B737 Captain reported receiving an Aircraft Release with an excess amount of fuel on landing at an airport with a forecast of rain.
Date: 201209
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: Marginal
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Physiological - Other; Distraction; Situational Awareness; Troubleshooting; Time Pressure
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; Flight Crew Took Evasive Action; General Declared Emergency; General Maintenance Action; General Physical Injury / Incapacitation
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Shortly after passing 10;000 FT in our climb; the Lead Flight Attendant called to inform us of a strong electrical smell in the forward galley area. Our conversation included old food in the ovens or coffee that had spilled onto the hot pad. In the cockpit; we only had a faint smell of cheap perfume or a weak solvent. The consensus was that the odor was dissipating after a few minutes; but 5-10 minutes later the Lead Flight Attendant called to say that she and 2 other flight attendants were experiencing respiratory distress (burning throats; irritated nasal passages) as well as irritated eyes. The First Officer and I didn't notice any irritation; but elected to go on oxygen as a precaution and declared an emergency and diverted back to the departure airport. The Lead Flight Attendant was cared for by a paramedic/passenger and then was cared for by paramedics that had met the aircraft at the gate. I don't know what caused the event; but the number one engine had been replaced and this was the first revenue flight for that engine. The IDG oil cooler on that same engine was also replaced during the same maintenance session. When cabin odor reports are submitted; an extensive checklist is followed to try to isolate the source of the odor. Why not use the same checklist to inspect the aircraft any time a piece is replaced that has a direct contact with the pneumatic system or air recirculation. One step further would be a requirement for a test flight.




Synopsis: An A320 Lead Flight Attendant became ill after a strong electrical smell developed in the forward galley during climb; an emergency was declared and the flight returned to the departure airport.
Date: 201712
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Ramp ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew; Person Ground Personnel
When detected: Taxi
Result: Aircraft Aircraft Damaged
Contributing factors: Company Policy; Human Factors
Primary problem: Company Policy

Narrative: Turning left into the gate I was at about 9 knots at beginning of turn with the right engine shut down. The thrust was approximately 35% N1 to maintain forward momentum to this uphill gate. When nearly aligned with the lead in line; marshaller indicated to stop. Maintenance towed aircraft to gate. There was a line of cans behind the flight line; and I believe lining them up (air can't escape) and being empty contributed to one of the cans tipping onto a Caravan behind the cans. Either have no cans (at least empty ones) behind line and in front of the feeders where the jet blast can topple them into aircraft.




Synopsis: B757-200 Captain reported during single-engine taxi to the gate; jet blast knocked over a can behind the flight line into a Caravan. Crew shut down and obtained a tow to the gate.
Date: 202106
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Other Freight Handling
Result: General None Reported / Taken
Contributing factors: Company Policy; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Environmental hazardous spill occurred today at ZZZ. One piece out of a total of 18 located on a skid was punctured releasing product inside while being transported by forklift to the export dock for customer delivery. The trail of the product was identified by the label as CO-FLAKE HZ with the aquatic toxicity label and UN3077 identifier. The spill was immediately contained and Dangerous Goods Specialist was notified to confirm level of hazard. Environmental Coordinator was then notified and instructions were given on cleanup procedures. Product located on floor was then placed in Dangerous Goods container until proper disposal as instructed. Instructions were then given on proper repackage procedure and the customer was notified.




Synopsis: Air Carrier Freight Personnel reported a Hazmat spill while being transported by forklift for customer delivery. Spill was corrected in accordance with DG procedures.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: Mixed
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class B ZZZ; Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Electrical Distribution
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Time Pressure; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [Priority handling was requested] with ZZZ Center on an IFR flight plan. [This] was requested because of a total loss of electrical power in the cockpit. I maintained radio contact with center for a few minutes and advised them that I was deviating to ZZZ (the nearest airport) I gave them my personal information and canceled my flight plan once on the ground. There was no destruction of property or injuries to report.




Synopsis: Pilot reported loss of aircraft electrical systems and diverted to landing at the nearest suitable airport.
Date: 202008
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On the initial climb after takeoff; I noticed we were flying 10 kts. slower than normal and only maintaining level flight. Immediately after I noticed that; my student and I heard a popping sound and the airplane started to shake. I looked at the tachometer and noticed the RPM decreasing; so I pulled the power to idle; put in full flaps; and held a full slip to land back on the runway. I did this since we were experiencing a partial engine failure. My student and I were okay; and we were able to taxi the airplane back to the Ramp.




Synopsis: C-172 Flight Instructor reported encountering a partial engine failure immediately after takeoff.
Date: 201909
Local time of day: 1201-1800
Location: CHS.Airport, SC
Flight conditions: Marginal
Weather elements / visibility: Rain
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Corporate
Operating under: Part 135
Flight plan: IFR
Flight phase: Taxi
Airspace: Class C CHS
ATC / advisory: Tower CHS
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Procedure

Narrative: We were cleared to taxi out from [FBO] [at] CHS via Taxiway G to Runway 33. After we completed our taxi check; and while on Golf; the First Officer switched to Tower frequency and reported that we would be ready reaching the runway. The Tower controller cleared us to line up and wait on Runway 33. The First Officer read back our clearance and I turned our anti-collision lights on. As we made the dogleg turn at the end of Golf I looked out to verify final was clear. As I did I saw landing lights that appeared to be on short final for 33. I immediately brought the plane to a stop and called Tower to verify we were cleared to line up and wait. Tower replied with the instruction to hold short of Runway 33. I replied that we were already over the hold short line. Tower then instructed the aircraft in short final (a [commercial] 737) to go around. After that point; Tower again instructed us to line up and wait; and shortly thereafter cleared us for takeoff. When we were handed off to Departure; the Departure Controller informed us there was a possible pilot deviation and gave us a number to call. The remainder of the flight proceeded without incident. After the conclusion of the flight; the First Officer and I called the number for CHS and spoke with [personnel] who identified himself as a Tower and Radar Supervisor. We discussed the incident and described what we had seen and heard and when. He agreed with our assessment that we had incorrectly been cleared on to the same runway another aircraft had been cleared to land on. Continued awareness of/focus on runway incursions; in this case on the part of the Tower Controller.




Synopsis: CE525 Captain reported ATC issuing LUAW instructions with B737 on short final resulting in runway incursion.
Date: 201309
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: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class G ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Powerplant Fuel System
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Human-Machine Interface
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 Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: After pre flight inspection I stuck the pilot side fuel tank it registered 13.5 gallons I did not visually check the right tank but both left and right gauges were reading the same; over 10 gallons each. Less than 15 minutes into the flight when I went to lean at 4;000 FT the engine sputtered I enrichened the mixture; no change. I notified Approach that I was zero fuel and needed an airport to land at. She gave me an airport and asked my intentions. I responded I would land there. Upon landing the engine restarted and I was able to taxi to fuel pump where the attendant pumped 43 gallons. I think that I had a blockage in the gascolator drain line and did not close the valve properly as I had gotten about 2 inches of fuel in the strainer and the fuel had stopped flowing I thought I had closed the valve. I guess while in flight the blockage came out and I lost fuel from the partially closed valve. After filling and checking for leaks I filed an IFR flight plan and flew home.




Synopsis: C172 pilot reports engine failure due to fuel starvation at 4;000 FT and is vectored by ATC to a suitable airport. It is thought that the gascolator drain valve did not close properly during preflight allowing over twenty gallons of fuel to be lost in 15 minutes of flight. Forty three gallons of fuel are added before continuing.
Date: 201404
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Runway insight on final approximately 1;400 feet AGL flying pilot called for flaps 30 landing checklist. I selected flaps 30 and noticed an ECAS message 'Trailing edge flaps'; the flaps remained at 25 with the flap handle selected to 30. I asked if he noticed any 'Roll' in one direction or the other. He said 'No' I then selected flap handle back to 25 and informed him of the trailing edge flaps ECAS message. At this point we were at 1;000 AGL and stable on final; I elected to land rather than go around in order to run the QRH checklist since the flaps were at 25 with no noticeable roll. Once on the ground we attempted to retract the flaps but they remained at 25; I'm not really sure if the flaps would have retracted if we had attempted a go around.




Synopsis: B757 Captain reports flaps remaining at 25 when flaps 30 is selected and an EICAS message for trailing edge flaps disagree. The flap handle is moved back to 25 and the First Officer continues the approach to landing. The flaps will not retract after landing.
Date: 202008
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Haze / Smoke; Turbulence; 6
Aircraft: Cessna 340/340A
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Final Approach
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Air Taxi
Reporter function: Single Pilot; Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Troubleshooting; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Gear Up Landing; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: The aircraft suffered an engine failure during cruise flight. The pilot secured the engine; advised ATC; and diverted to the nearest airfield. With adverse wind conditions the pilot elected to go around on final. The aircraft would not climb or accelerate. To avoid an off airport crash; the pilot reduced power to idle and landed gear up on the remaining runway. The aircraft came to rest at the departure end of the runway. The event did not result in any injuries and there was no evidence of substantial damage.




Synopsis: CE340 pilot reported single engine landing attempt with failed go around resulting in gear up landing on runway.