elihoole/asrs-aviation-reports huggingface dataset:
Date: 201408
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Dash 8 Series Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Aircraft component: Normal Brake System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Flight Crew Became Reoriented; General Physical Injury / Incapacitation
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Flight Attendant was knocked off of her feet after the engine was brought up out of feather and was injured when the aircraft rolled forward and was stopped using the emergency brake. The Before Start Checklist had been run and the parking brake and pressure was at least 2;600 PSI; which matched closely to what I had seen on my preflight walk around. The engine starts had happened without incident and I had just finished verifying my flow action items and was waiting for the Captain to start up the Number 1 Engine. After I verified my flow I turned the packs on and was the waiting for the Number 1 Engine to start. Once the Number 1 Engine was started I was then waiting for the Captain to bring the condition levers out of feather to run the auto feather power uptrim tests and PTU manual test. The Captain brought the condition levers up and I reached down to start my tests then felt the aircraft move forward. The flaps had been set to 5 degrees and when the aircraft moved forward it looked like the Captain tried to stop the aircraft with the normal breaks; but had to use the emergency brake. The aircraft came to a stop and the Captain immediately started to shut the airplane down and check on the Flight Attendant. In the whole situation I can't remember ever seeing when the parking brake had disengaged.The Captain called the Flight Attendant and found that she had been injured. I am not sure why the event happened the parking brake had been set and I was sure that when the checklist was run that it had been set properly when I had looked over. The aircraft was shut down and secured and the Captain called for medical assistance from the ground crew First Officer made sure that the aircraft was shut down and secured. Make sure that you have normal braking before removing the chocks to make sure we have two ways of stopping the aircraft.




Synopsis: DHC8 First Officer reports his aircraft rolling forward as the Captain brings the condition levers out of feather after engine start. Normal braking is attempted to no avail and the emergency brake is used; stopping the aircraft abruptly and injuring the Flight Attendant.
Date: 202003
Local time of day: 0001-0600
Location: ZZZ.TRACON, US
Flight conditions: IMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On descent experienced a fume event. After landing the fume event was noted in the aircraft log.




Synopsis: A320 First Officer reported a fumes event during descent.
Date: 201211
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B737-800
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: Horizontal Stabilizer Trim
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise flight the 'Stab Out of Trim' light illuminated. We performed the 'Stab Out of Trim' QRH Procedure and the stabilizer did not respond to electric trim inputs. We then accomplished the 'Stab Trim Inoperative' Checklist and were able to use the operative manual trim wheel for controlling trim. We declared an emergency with Center and accomplished an uneventful Flaps 15 landing at our destination.




Synopsis: When their stabilizer electric trim failed at cruise the flight crew of a B737-800 completed the associated QRH procedures and landed at their destination utilizing flaps 15 and manual control of the stabilizer trim.
Date: 201206
Local time of day: 0601-1200
Location: SFO.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B SFO
ATC / advisory: Tower SFO
Aircraft component: Squat Switch
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; General Maintenance Action
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: We were flying the FMS Bridge Visual to Runway 28R at SFO. When we put gear down; we received several ECAM messages all of which appeared related to the air/ground landing gear sensor. The ECAMs we were reviewing in rapid succession below 2;500 FT and during a very high workload phase of flight included: Anti-Ice Standby pitot; Cabin Pressure Landing Elevation Fault and just then the FMC 'dumped!'We quickly realized we could no longer accomplish the FMS visual without the FMS being initialized and reinstalling the approach; which would have dramatically increased workload during what was already a very busy approach. We felt the greatest threat was having the First Officer go 'heads down' at this late a stage in the approach. Therefore; we called the Tower and reported our loss of navigation equipment and inability to complete the FMS approach. We advised we had preceding aircraft and the runway in sight. He then cleared us for a Visual Approach to Runway 28R. After landing; as we were pulling into the gate; we received a Landing Gear System Disagree ECAM. We contacted Maintenance Control and Dispatch as well as Line Maintenance. Due to time constraints we did not attempt to reinitialize the ACARS and send maintenance codes for the affected systems. We instead printed out the last leg ECAM report; gave it to the Line Mechanic and asked Maintenance Control to put the squawks into the maintenance computer.




Synopsis: While below 2;500 FT MSL flying the BRIJJ RNAV Visual Approach to SFO; an A319 flight crew received multiple ECAM warnings related to the possible failure of the air/ground squat switch. In addition their FMS failed leaving them without RNAV capability. They asked for and received a 'conventional' Visual Approach Clearance from the Tower and landed uneventfully.
Date: 201506
Local time of day: 1201-1800
Location: P50.TRACON, AZ
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Flight plan: IFR
Flight phase: Climb
Airspace: Class B PHX
ATC / advisory: TRACON P50
Reporter organization: Government
Reporter function: Approach; Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Situational Awareness; Time Pressure
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was a departure off of SDL; he was given an altitude of 070 and direct to the first fix in our airspace.  I climbed him to FL210. He read it back but wasn't climbing well he was headed for higher terrain so I issued a vector to clear.  Once I saw he was descending and I verified he was on the appropriate altimeter setting as this has happened quite a few times to pilots in the last week.  I asked if he had the terrain in sight; he said he was looking for traffic.  I had given him two vectors to clear terrain he read back both but never turned to the first heading I gave but took the second vector.  I asked if he had the terrain in sight and needed assistance; he replied he was looking for traffic and needed no assistance.




Synopsis: A Phoenix TRACON (P50) Controller reports of a pilot issue with communications. The Controller climbed the aircraft to a higher altitude; but it wasn't climbing well. The Controller asked the pilot if he had the terrain insight and issued two vectors away from the higher terrain. The pilot reported he was looking for traffic. The Controller continued to vector the aircraft; and the pilot took the second heading.
Date: 201908
Local time of day: 0601-1200
Flight conditions: VMC
Aircraft: Seaplane or Amphibian
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Descent
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Airspace Structure; Procedure
Primary problem: Procedure

Narrative: During routine seaplane training operations at Lake Berryessa in Northern California; we encountered 2 unexpected; unannounced; tethered paragliders operating between the surface of the lake and up to 3;500 feet or higher. The paragliders were not operating on a day that was scheduled for operations per their website; there was no NOTAM; and we were unable to reach them on the lake frequency; the agreed frequency to communicate on with them.  We saw them in time to do avoid collision conflict with them. However; the main danger with them is the tether line which is basically invisible.  When we're conducting water landings at low altitude and they're up at 4;000 feet on a tether to a boat; there's no way for us to see it; and it poses a significant safety hazard to both our flight operations and their paragliding operations.




Synopsis: Pilot reported encountering two tethered paragliders at 3;500 feet above a Lake Berryessa requiring evasive action.
Date: 201204
Local time of day: 0601-1200
Location: GRB.Airport, WI
Flight conditions: Mixed
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class C GRB
ATC / advisory: TRACON GRB
Aircraft component: Altimeter
Component problem: Improperly Operated
Reporter organization: Corporate
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion
Second reporter function: Pilot Flying; Captain
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The altimeter setting was entered incorrectly from the new ATIS given by ATC over the radio (Approach Controller). The altimeter was entered 30.38; the correct setting should have been 29.38. ATC advised a low altitude alert; the crew corrected the altitude; and altimeter setting. The crew was at the time of the alert in VFR conditions and continued with a visual approach to Runway 24 at GRB.


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


Synopsis: A Corporate Jet flight crew entered 30.38 in the altimeters on visual approach to GRB; but received an ATC low altitude alert because the actual altimeter was 29.38.
Date: 201901
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Trailing Edge Flap
Component problem: Malfunctioning
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
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During a visual approach and while configuring the aircraft for landing; the trailing edge flaps failed to extended past 8 degrees. The flap failure occurred approximately 5 miles from the runway threshold and a missed approach was executed. The flight crew performed the Trailing Edge Flaps Disagree Checklist which eventually required manual extension of the trailing edge flaps using the Alternate Flaps Extension System. Subsequently; the flight crew was cleared for an ILS approach; extended the trailing edge flaps manually; and landed with flaps 15 without further issue. It should be noted that never were any flap extension speeds exceeded.




Synopsis: B737 First Officer reported trailing edge flaps failed to extend; crew executed a go-around and landed with flaps 15 using the manual extension system.
Date: 201302
Local time of day: 1201-1800
Location: CMA.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class D CMA
ATC / advisory: Tower CMA
Reporter organization: Personal
Reporter function: Pilot Flying; Captain; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness; Distraction; Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: I had received clearance to land and had been advised traffic position behind a Mooney on base leg which I had observed when another aircraft overtook me on the final approach track; about 100 feet directly above me and landed in front of me. I initiated a go-around just before the threshold; called by ATC; and completed a visual circuit and landing. The airport environment had seemed very busy with multiple inbound and pattern traffic from different directions.




Synopsis: An aircraft on very short final to CMA had a near miss when an aircraft which over took it landed ahead so the pilot executed a go-around; called Tower and returned to land.
Date: 201808
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff
Contributing factors: Aircraft; Procedure
Primary problem: Procedure

Narrative: On clearance for takeoff; First Officer; Pilot Flying; set initial power setting to %50 N1. He didn't like how slowly one engine was accelerating to %50 versus the other one so he pulled the throttles back to idle. Since this was a rolling takeoff we had no choice at that point but to reject. So we cleared off the runway. As the Captain with 2;000 hours in this aircraft I didn't see that the delay between engine accelerations was all that abnormal. So we talked about letting the engines stabilize at %50 with brakes set on our next takeoff. We got back in line and re-ran all the checklists. On takeoff we left the brakes on while setting %50. Engine accelerations were normal so we went on our way.


Second narrative: First Flight of day. I was flying pilot. Airbus had CFM engines. Cleared for takeoff. Brought thrust levers to 50%. Held brakes. Left engine accelerated to 50%. Right engine did not accelerate normally. Was at about 5 to 10% when the right engine was at 50%. I released the brakes and immediately set thrust levers to idle and exited runway. We were heavy and Captain aborted takeoff. Max speed was less than 20 KIAS or so. Taxied off; got back in line and took off normally.


Synopsis: A321 flight crew reported that first flight of the day the Number 2 engine was slow to spool.
Date: 201911
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Citation Excel (C560XL)
Operator: Fractional
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Elevator Trim System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At rotation speed; PIC called rotate I pulled back on the yoke smoothly too full aft position and the airplane did not rotate. Yolk felt extremely heavy and after a few seconds it finally rotated. In-flight we noticed the trim indicator seem to be father aft than other airframes we have flown. I believe the pitch trim is rigged to far aft on this airplane.




Synopsis: CE-560XLS First Officer reported aircraft was slow to rotate on takeoff.
Date: 202103
Local time of day: 1201-1800
Location: ZZZZ.ARTCC, FO
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZZ
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Electronic Device; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Passenger
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During cruise; a flight attendant advised us via the interphone that a cabin fire was occurring; without going into detail. We prepared for the possibility of diverting to the nearest suitable airport; but after conferring with the cabin crew; the Captain determined that the fire was the result of a cell phone with an overheated battery being tossed into the aisle and burning a small area on the carpet. The smoldering carpet was extinguished; and the phone battery was cooled and placed in the thermal containment bag. We continued to ZZZ1 without further incident.




Synopsis: B757 First Officer reported a passenger's overheated cell phone caused a small carpet area burn. Flight continued uneventfully after extinguishing smoldering carpet and cell phone placed in a thermal containment bag.
Date: 201401
Location: ZZZ.Airport, US
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Cargo Door
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Gate; Flight Crew Rejected Takeoff
Contributing factors: Procedure
Primary problem: Procedure

Narrative: [We] aborted takeoff at approximately 80 KTS due to ECAM for aft cargo door open indication. [We] returned to the gate. Maintenance found the door handle out of the stowed position. No maintenance action required. Topped off fuel and departed uneventfully.




Synopsis: An AFT CARGO DOOR OPEN ECAM alerted during takeoff; so the takeoff was rejected. At the gate the door handle was found out of place; closed properly; fuel topped off and the flight departed uneventfully.