elihoole/asrs-aviation-reports huggingface dataset:
Date: 201310
Location: ZZZ.TRACON, US
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb out encountered left engine limit surge stall high EGT and vibration. We leveled off and power came back and left engine was then operating within limits. However there was some vibration. We declared an emergency. We then completed the Engine Limit Stall Surge Checklist and chose to keep engine running. We advised ATC that we wanted to return. We briefed flight attendants to expect a normal landing and we would be landing within five to ten minutes. ATC gave us vectors for the ILS. We had a normal smooth landing at 206;000 LBS. We cleared the runway and shut down the left engine. Emergency vehicles followed us to the gate.


Second narrative: Climbing out at about 4;000 FT the Number 1 Engine EGT spiked into the red and the engine started to surge. This only lasted a few seconds. I flew the airplane and talked to ATC while the First Officer pulled out and read the engine limit surge checklist. I declared an emergency and told ATC that we needed to return. I sent an ACARS message to Dispatch and had the First Officer advised the flight attendants and the passengers of our intentions. All engine indications were normal by this time so we left the engine running as per the checklist. Descent and approach were normal except for a slight airframe vibration. On short final at 1;000-800 FT; the Number 1 Engine again started to surge. Landing was imminent so we continued to a smooth landing. No reverse was used. Taxied off the runway and shut down the Number 1 Engine. Taxied to the gate and parked.


Synopsis: B757 flight crew experiences high EGT and engine surging climbing out of 4;000 FT. Checklist procedures are complied with; an emergency is declared and the flight returns to the departure airport.
Date: 201707
Local time of day: 0001-0600
Location: CLT.Airport, NC
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Tower CLT
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport; Procedure
Primary problem: Procedure

Narrative: Aircraft X was pushed back; tail pointing North at the CLT South Ramp; parallel to 'C' taxiway; between exit C3 and C4. After ground personnel disconnected from aircraft; he accelerated his engine to taxi out thru C3 exit to 'C' taxiway. His tail once he turn to C3 exit; the tail pointed to the West where [multiple] facility are. Due to the aircraft engine acceleration to taxi he blew several containers causing damage to them. One of these container blew in the air and flew over the head of one of the Ramp Agents; which he dodged to the floor for security.According to the report [of the] ramp supervisor; this same incident happen [before]; also blowing containers off the carts. During both incidents; nobody got hurt or suffered physical damage.CLT Station Supervisor instructed the push back crew; going forward not to push aircraft back between C3 and C4; instead to position aircraft between C2 and C1; this will force the Tower to clear [aircraft] to taxi exiting C1.Also I suggest that a Directive Note should be issue to CLT Tower to advise them not to clear aircraft to exit C3 to taxi to 'C' taxi way due to safety.




Synopsis: A station supervisor reported aircraft engine acceleration during taxi blew several containers causing damage to them and nearly hitting an agent.
Date: 201809
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Challenger 650
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Aircraft component: Horizontal Stabilizer Trim
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness; Time Pressure
Second reporter function: Pilot Flying; First Officer
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: Cruising at 4000 feet and 250 knots; stab trim and associated Mach trim amber CAS messages displayed. Unable regain control of stabilizer trim. Diverted [and] landed with reduced flap setting per [the handbook]. Min speed to maintain elevator pitch control 150 knots.


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


Synopsis: Bombardier Challenger 650 flight crew reported a failure of the horizontal stabilizer trim.
Date: 202002
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Weather elements / visibility: Fog; Rain
Light: Daylight
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; 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: Was training in low vis. weather. Received clearance down to 2;100' out of 3;000'. Was focused on ForeFlight (confirming no towers; trees; other obstacles were in the area) and looking outside the plane (trying to see the ground) and drifted below my clearance. [ATC] asked me my position at the time I saw the field (I forgot to call the field at this time). I stated I was a few miles southeast of the field level at 1;200' at which time [ATC] issued a check altitude immediately alert. I once again stated my position and called the field. I was told to squawk VFR and changed frequencies and was advised to not do this again. I acknowledged and landed.




Synopsis: PA-28 pilot reported receiving a low altitude alert from ATC on approach.
Date: 201912
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
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: Engine
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)
Second reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [At] flight level 340; south of ZZZ; direct ZZZZZ; [the] oil quantity showed 8%. The Captain called Maintenance Control while I flew. I referenced drift down altitude; speed from the FMC and referred to the QRH for low oil pressure checklist and the following engine shutdown checklist since low oil quantity is not included.At approximately XA29; Engine Number 1 oil quantity at 0% and engine oil pressure began fluctuating from 45 PSI to 33 and lower in the amber band. By XA40; oil pressure was approaching red band. At approximately XA40; the Captain and I shut down Engine Number 1. The Captain and I decided along with Dispatch; after discussing with Maintenance Control; that ZZZ was the best location to divert to. I accomplished a visual landing to Runway XXL; backed up by the ILS XXL. Winds were 330/7; autobrake 3. Crash recovery/fire looked over the aircraft after the landing. All clear; we taxied to Gate XX. Taxi on to the gate was uneventful. This does not include all actions that were performed but those I can recall from memory [that] feel important.


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


Synopsis: B737 flight crew reported a loss of oil quantity and drop in oil pressure in the Number 1 Engine and decided to shut the engine down and divert. An uneventful landing and taxi in was made.
Date: 202104
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Piper Single Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: UNICOM ZZZ
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Weather / Turbulence; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: Training a student on crosswind landings. The wind picked up and the taildragger looped on the ground.




Synopsis: X Cub Instructor reported student's loss of directional control during crosswind landing training resulting in a ground loop.
Date: 201303
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: IAI1124/1124A Westwind
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Elevator Trim System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The elevator trim control malfunctioned during climb out. The pilot in command declared an emergency. The elevator was unresponsive and slow moving. With help of the non-flying pilot; we brought the airplane back around and landed.




Synopsis: The pilots of a Westwind experienced an elevator trim control malfunction. With the help of the non flying pilot; they made a successful landing.
Date: 201211
Local time of day: 1201-1800
Location: IAD.Airport, DC
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower IAD
Aircraft component: Turbine Engine
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown; Distraction; Situational Awareness; Fatigue; Communication Breakdown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We taxied to Runway 30 in IAD. All checklist and procedures were called for and accomplished normally. We were given a takeoff clearance as we were taking the runway. I transferred controls to the First Officer and he immediately noticed the number one engine was not running. We canceled our takeoff clearance and cleared the runway. The engine start/stop selector was in the stop position. I determined that in the absence of an EICAS message; the engine had not spontaneously shut down and could be safely restarted. Having accomplished this; we were instructed to taxi to the runway and a normal flight was conducted.Complacency; after many hundreds of takeoff cycles; it sometimes becomes so routine that vigilance can suffer. Also; the day prior; I had worked a 1435 hour duty day with multiple deadheads and a short overnight; so fatigue can not be ruled out as contributory.


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


Synopsis: An air carrier crew realized after taking the runway that only one engine had been started and so exited the runway to start the engine before completing a normal takeoff.
Date: 201302
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Turbulence; 5
Aircraft: Cessna 340/340A
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Workload; Human-Machine Interface; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; Flight Crew Diverted; General Declared Emergency
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Departed with one passenger; full fuel; normal IFR departure and climbed to 10;000 FT. Heard a high pitch wine from an unknown source; engine instruments were in the green and appeared normal. One minute later; I noted lose of turbo charging on right engine. I adjusted for engine fuel richness and monitored temperatures. While reaching for the checklist; the engine started running in fast then slow oscillations; about 4-5 times and then quit. Temperature appeared normal. I secured the engine and feathered the prop. All appeared to happen within 1-2 minutes. Notified ATC of engine out and needed to declare for landing. Entered the clouds at 8;000 FT MSL; flew vectors to ILS; had a 22-26 KTS turbulent left crosswind on the localizer. Winds; upon breaking out of clouds at 700 FT AGL; were 5-10 KTS. I experienced moderate turbulence and difficulty maintaining airspeed and directional control until touchdown. Landed softly and taxied to FBO without a problem. Thanks to the Controller for a soft; calm voice throughout the event. Aircraft was out of annual for 6 hours; no problems during the prior trip. During single pilot IFR emergency operations; can ATC offer/suggest/read the emergency checklists? It would have helped reducing pilot workload and better prepared the aircraft and pilot for off airport landing. Example: gear and flaps up until can be runway made. I dropped the gear and lost airspeed that was hard to make up.




Synopsis: C340 pilot experienced an engine failure shortly after leveling off at 10;000 FT. An emergency is declared and flight diverts to the nearest suitable airport. The pilot reports difficulty managing the emergency and flying the single engine ILS in IMC and turbulence as a single pilot. The gear is extended early resulting in difficulty maintaining approach speed.
Date: 201606
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna Citation Sovereign (C680)
Operator: Fractional
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
Component problem: Failed
Reporter organization: Fractional
Reporter function: Pilot Not Flying; Captain
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: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: In our climb to FL400; passing through FL310 we received a CAS message for ENG FIRE DETECT FAIL L. We complied with the checklist and decided on a precautionary landing as soon as practical. I then called the Assistant Chief Pilot (ACP) on duty to ask whether we should return; or if there was a better diversion airport that would accommodate our passenger. The ACP was advised of our situation and position; and his first response was asking if we could continue to our destination. There was no way we should have even been questioned as to continuing the planned flight with this type of malfunction. After he consulted with scheduling; the ACP; asked us to go back to the departure airport. This was the best option for the situation and passenger accommodation. My SIC and I had already discussed that it was where we thought best; however we went through the chain of command per company procedure.This particular ACP is less than capable for his position. He rushes to make judgements without consulting with crews or his resources. In no way; knowing what he did about the malfunction; should someone in his position suggest continuing a flight for 90 minutes without a fire detection system. I have less confidence than ever in this particular ACP. Posing such a question without hesitation or thought could lead a crew to put the aircraft and passenger in a dangerous situation if the flight were to continue to the destination.




Synopsis: CE680 Captain reported receiving an ENG FIRE DETECT FAIL L climbing through FL310. After complying with QRH procedures the company was contacted for a diversion airport. The duty pilot first suggested that the crew continue to destination; before agreeing that a return to the departure airport was the best option.
Date: 201206
Location: ZZZ.Airport, US
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Parked
Aircraft component: Exterior Pax/Crew Door
Component problem: Improperly Operated; Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Aircraft

Narrative: I had armed Door 5L and cross checked 5R when the 'arm doors' announcement was made by the Purser. After the cocktail service another Flight Attendant informed me that door 5L was not armed. My reaction was not an alarmed one as I knew I had armed the door but I proceeded to 5L where some customers were congregating. One of them sitting in my jumpseat and had a carry on bag on top of the door. I advised them not to sit in our jumpseats at either door. I then checked and determined the door wouldn't remain armed as the handle was like a spring that kept going back to the disarm mode. Maintenance was advised and a Mechanic came on board after landing. Another Flight Attendant had also witnessed the conditions and confirmed my observations to the Mechanic that the handle was like a 'spring.'




Synopsis: While en route the Flight Attendant/Reporter who had armed door 5L prior to departure on a B747-400 was advised it was no longer armed. When the reporter investigated she discovered the arming door would not remain in the armed position but; instead; would spring out of it when arming was attempted. Maintenance was advised and met the aircraft upon arrival.
Date: 201508
Local time of day: 1201-1800
Location: M98.TRACON, MN
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B MSP
ATC / advisory: TRACON M98
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Time Pressure; Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Procedure; Human Factors
Primary problem: Procedure

Narrative: Approach told us to descend [at a] good rate down to 6;000 feet continued by a descent to 4;000 feet. While descending approach notified us that we had left the class Bravo and we immediately realized we were doing 250 below the class Bravo shelf.Doing 250 knots in the Class B; complying with an ATC clearance and descending at our best rate quickly put us below the Class B momentarily before the next lower shelf.Better awareness of this type of scenario happening. Now that I have seen how this can play out.




Synopsis: An air carrier on arrival to MSP was given an expedited clearance to 6;000 feet followed by clearance to maintain 4;000 feet. The flight descended out of MSP Class B at 250 KTS.