elihoole/asrs-aviation-reports huggingface dataset:
Date: 201205
Local time of day: 1201-1800
Location: T31.Airport, TX
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-32 Cherokee Six/Lance/Saratoga/6X
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class E T31
ATC / advisory: UNICOM T31
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On approach to landing on Runway 17 at T31 (Aero Country Airport); I misread my chart for the Traffic Pattern Altitude. Instead of approaching at an altitude of 1;600 MSL; my altitude was 1;000 MSL; putting me only 200 FT above the ground and surrounding homes. [This was] a mistake that will not happen again. A more thorough pre-brief will prevent this from occurring in the future.




Synopsis: A PA-32R pilot reported misreading the chart and descending to 200 FT AGL in the pattern at T31.
Date: 201305
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Other Skydive School
Operating under: Other Part 105
Flight plan: None
Mission: Skydiving
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Malfunctioning
Reporter organization: Other Skydive School
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While climbing over the airport; partial loss of engine power occurred at 6;000 feet. I declared an emergency engine out and stated my intention to land. At pilot's discretion I idled the engine and landed without incident. No damage to persons or property.




Synopsis: C182 pilot climbing out over the airport with skydivers experiences a partial loss of engine power and glides back after declaring an emergency.
Date: 201908
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Final Approach
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Bombardier/Canadair Undifferentiated or Other Model
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Communication Breakdown; Confusion; Situational Awareness; Time Pressure
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: As a C172 in the pattern; I saw a regional jet on taxiway in holding short runway XX. I was abeam the 1000 footers and made a radio call to the traffic in the area that I could do a circle around the field if the jet was ready for departure. The jet responded 'no; you should be fine.' I called my base turn and saw the jet move onto the runway; so called 'go around' and flew over the jet that had moved to the end of the runway. I sidestepped left; then made a left turn out of the way of the jet. Everybody at ZZZ saw it happen and heard on the radios and asked me if I was ok and can corroborate the story.




Synopsis: GA pilot reported going around due to a conflict with a departing regional jet at non-towered field.
Date: 201402
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Vehicle Driver
Human factors: Other / Unknown
Second reporter function: Ramp
Anomaly: Ground Event / Encounter Vehicle; Ground Event / Encounter Object
Detector: Person Ground Personnel
When detected: Taxi
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Airplane on the ground. I went out to drive the electric tug with the cart on the other side.  Then the plane [was] coming. He's already on the line then the [marshall] is receiving the plane. Then I just saw the plane stop and heard the loud noise.  I looked underneath the plane and saw the cart tilted.


Second narrative: I was in the ready room waiting for my flight to come in. As soon as the monitor showed that the aircraft was on the ground I went outside to look for my lead and gate crew who were not out there. The aircraft was already on the line waiting to be brought in. I went back inside to look for my gate crew and did not see them in there; so I went back outside and saw that I had a wing walker out there ready to help bring the aircraft into the gate. I walked out to the gate to marshall in the aircraft; so it did not have to wait on the rest of the crew to arrive. I took a quick look at the operational safety zone to see if there was any FOD or equipment in the way and it did not appear to me that there was. I was in a bit of a rush to get the aircraft in; so I did not do a FOD walk 5 minutes before it came in. My wing-walker was on the Captain's side of the aircraft walking it in as I started to bring it into the gate. The front tires were a little off the line as it was coming in; so I was paying a lot of attention to making sure that he started moving back toward the lead in line and not veering away from it. The pilot started to steer back towards the center of the line and it was getting to the point in which I had to start slowing him down to stop and it was at that point that I heard a loud bang and I looked over at the copilot's side and saw that the wing tip had hit a baggage cart sitting at the edge of the operational safety zone possibly because I had a hood over my head because it was cold and windy. I then gave the X stop signal to the pilot. I did not see the baggage cart sitting there when I looked over the gate as I was on my way out to marshall him in. After everything had stopped I went inside to get a Supervisor.


Synopsis: Three ramp personnel describe a wingtip collision with a bag cart during marshalling.
Date: 201205
Local time of day: 0601-1200
Location: ZAB.ARTCC, NM
Flight conditions: VMC
Weather elements / visibility: Turbulence
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight phase: Cruise
Airspace: Class A ZAB
ATC / advisory: Center ZAB
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: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Speed All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Aircraft; Weather
Primary problem: Weather

Narrative: In cruise FL390 we encountered strong wave action over ABQ VOR. Airspeed increased 10 KTS and altitude increased plus 200 FT. The autoflight system corrected with a large thrust reduction. Then our airspeed dropped 30 KTS and altitude dropped 400 FT from our peak. We nosed the aircraft down in an effort to maintain airspeed. I called ATC and advised them of our immediate descent. We encountered moderate turbulence during the descent. We leveled at FL370. No injuries to passengers or crew because they were seated and galleys were secure. No airframe limits were reached. No traffic conflicts were encountered.


Second narrative: The mountain wave had been reported as moderate; but I thought our experience was moderate to severe.


Synopsis: A B737-800 encountered a mountain wave encounter that caused large airspeed and altitude excursions.
Date: 202006
Local time of day: 1201-1800
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Flight plan: VFR
Flight phase: Cruise
Aircraft component: Engine
Component problem: Failed
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Precautionary landing in a field due to engine failure.




Synopsis: C172 pilot reported precautionary landing in a field due to engine failure.
Date: 201910
Local time of day: 0601-1200
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Parked
Aircraft component: Aircraft Logbook(s)
Component problem: Improperly Operated
Reporter organization: Contracted Service
Reporter qualification: Maintenance Airframe; Maintenance Inspection Authority; Maintenance Powerplant
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Other Person
When detected: Pre-flight
Result: General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Human Factors; Logbook Entry; Aircraft
Primary problem: Logbook Entry

Narrative: Acting as an A&P with Inspection Authorization; I signed off an annual inspection for a Client. The aircraft was [later] involved in a hand propping occurrence.As a result; the FAA requested to see the aircraft logbooks. Upon review; they noticed that the form and field approval paperwork for the installation of the engine was not in the Logbooks.The engine has been on that aircraft for 30 plus years; and I have been familiar with said aircraft all of those years; so I assumed that the paperwork had been done; and the installation was legal.




Synopsis: Mechanic reported signing off an annual for an aircraft that was missing paperwork for an engine change.
Date: 201409
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Descent
ATC / advisory: TRACON ZZZ
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Critical; Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Received upper EICAS trailing edge flap asymmetry message. Declared emergency and ran appropriate QRH checklists. Landed using alternate flaps at less than position one per the QRH. Not able to determine the cause from information available on the flight deck.


Second narrative: QRH directed an Alternate flap extension to position 1. and a Vref F30 +40K approach speed. Declared an emergency with Approach control due to higher than normal approach speed and abnormal configuration.


Synopsis: A B757-200 flight crew complied with the applicable QRH; declared an emergency and landed with flaps one after receipt of a trailing edge flap asymmetry EICAS message.
Date: 201606
Local time of day: 1201-1800
Location: SCT.TRACON, CA
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B LAX
ATC / advisory: TRACON SCT
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Human-Machine Interface
Anomaly: ATC Issue All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: The STAR (Stadium) final scope lost all data tags and radar. Initially; the scope froze; then the tags dimmed; and finally the scope went black. This was during a busy Los Angeles arrival push. The controller leaned over and used the DNYR (Downey) scope next to him to provide services. STARS was installed a very short time ago.  We have seen an increase in software issues related to software updates 'STARS drops.'  A few weeks ago the STARS system was deemed unreliable and the traffic rate was drastically reduced. Many delays incurred. The controllers/FLMs [Front Line Managers] do not have confidence that the equipment is capable of delivering a consistent product. This was a total loss of data.




Synopsis: SCT ATC Front Line Manager reported losing all data tags on the Stadium Radar scope. The Front Line Manager reported the confidence level in the equipment is low due to a decrease in reliability.
Date: 202006
Local time of day: 0601-1200
Location: D01.TRACON, CO
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: Initial Approach
Airspace: Class B D01
ATC / advisory: TRACON D01
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Human factors: Confusion; Distraction
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC Overrode Automation
Contributing factors: Airspace Structure; Company Policy; Procedure
Primary problem: Procedure

Narrative: The TRACON continues to pair up aircraft on the parallel final approach courses for no reason. I was on the left runway and an Airbus on the right runway was approaching from behind and lower at a greater speed which then set off our TCAS. Neither aircraft were on a collision course but the close proximity set off TCAS. This continuing practice by the TRACON is dangerous and significantly increases workload in the most critical phase of flight. For some unknown reason; TRACON likes to pair up aircraft on the final approaches to the parallel runways inducing TCAS TA/RA events.The TRACON should not pair up aircraft on final for the parallel runways. This airport is not SFO in that operationally they do not need to pair up aircraft. The TRACON should stagger aircraft on the approaches for the parallel runways. Staggering will decrease flight crew workload; TCAS occurrences; and not affect traffic volume or flow to this airport.




Synopsis: E175 pilot reported receiving a TCAS alert for traffic on the parallel runway.
Date: 202110
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Dawn
Aircraft: PA-31 Navajo/Chieftan/Mojave/T1040
Operator: Other Aerial Survey
Operating under: Part 91
Flight plan: IFR
Mission: Other Survey
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Emergency Exit
Component problem: Malfunctioning
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Overcame Equipment Problem; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Procedure; Aircraft
Primary problem: Aircraft

Narrative: On DATE 1 while cleaning the aircraft I opened the emergency exit and verified its operation. I closed the emergency exit without issues. The handle was difficult to move into the closed position but it is usually difficult to move; as my normal procedure when being assigned to a new aircraft I open the emergency exit and verify its operation. I have opened and closed approximately 10 different Navajo or Aztec emergency exits in my last few years of my career. On DATE 2 I took off from ZZZ airport at XA:22z; and climbed to 8;000 feet enroute to an aerial photo mission. At some point in the climb I heard a little bit of air leaking from behind the co-pilots seat and could not determine its source. I Leveled off at 8000 feet at XA:33z. At XA:43z the emergency exit door came halfway open and then a few seconds later it departed the aircraft. I advised ATC that I was returning to ZZZ airport and landed with no further issues at XB:12z. Examination of the emergency hatch latching system shows at all 4 retention pegs appear to be in their correct engaged position and the emergency exit T handle is up and plexiglass clover is in place.




Synopsis: PA-31 pilot reported an air turn back after the aircraft emergency escape hatch opened in flight; then departed the aircraft.
Date: 202111
Location: AFW.Airport, TX
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Final Approach
Airspace: Class D AFW
ATC / advisory: Tower AFW
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot; Trainee
Reporter qualification: Flight Crew Student
Human factors: Training / Qualification
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors; Procedure
Primary problem: Environment - Non Weather Related

Narrative: Routine solo flight; after a couple laps in the pattern I trusted Tower to separate me from wake turbulence because this was my second solo and I was focused on learning how to fly solo. I encountered wake turbulence on final approach and performed a go around; but I was off course due to the wake and it felt like if I tried to come back to runway heading it would cause an unstable scenario. Lesson learned; always caution wake turbulence.




Synopsis: Light aircraft Student Pilot reported executing a go-around after encountering wake turbulence on final approach at AFW airport.
Date: 201308
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Aircraft component: Galley Furnishing
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Passenger; Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: The flight was an out and back. When we were departing for the return flight; the galley cart came out of the stowed area during takeoff. It was immediately caught by the passenger in 1C. I released my shoulder straps; but kept my lap belt on. This allowed me the ability to maneuver the cart with her (passenger in 1C) assistance; while not completely getting out of my seat during takeoff. I felt the situation would have been more unsafe with me out of my seat; and it could be handled with me still in the jump seat. I turned the cart to release the brake; because we couldn't really move it well with the brake on. Together we pushed it towards the galley service door; pinning it against the bulkhead. I watched it the entire time we were climbing to 10;000 FT; and she insisted on propping her foot up to make sure it stayed in place (instead of me reaching to hold it). When the 10;000 FT chime signaled; I stowed my jump seat before securing the galley cart back into position. The passengers in 1C and 1B informed me that they were not injured by the cart. The woman in 1C said it had only startled her. She was very understanding and kept reassuring me that she wasn't harmed. Another gentleman (I believe in row 3 or 5 B) asked if I was okay. The rest of the flight went without incident. In all honesty I believe this incident only occurred due to my lack of experience. This trip was my first trip after IOE. The instructors warned us during training that it will happen one time; and never again. Even though we kept the plane and I didn't have to perform a preflight check; commissary came aboard to groom the plane. They must have pulled the trash leaving the latch open; and I missed it. It was definitely a learning experience for me. Now I know to always triple check the galley latches. This isn't something I ever want to happen again!




Synopsis: CRJ-200 Flight Attendant reports a galley cart coming out of the stowed area during takeoff. It is corralled with the aid of a passenger in 1C and returned to its' normal position passing 10;000 FT in the climb.