elihoole/asrs-aviation-reports huggingface dataset:
Date: 201905
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate; Taxi
Result: General None Reported / Taken
Contributing factors: Company Policy; Procedure; Human Factors
Primary problem: Ambiguous

Narrative: I am not satisfied with the findings and explanation of a very serious situation. My airplane was loaded with an 18135 lbs. pallet over the nose. It was not supposed to have been loaded. The only fix I see is finger pointing as to who was wrong and nowhere do I see a prevention from it happening again. Outsourcing and communication on the part of [Company] load planning caused this mistake. I would like something more done and a better explanation as to how we will prevent this from occurring again. The closure of the report does nothing but sweep it under a rug.




Synopsis: A320 Captain reported cargo was loaded in error on the aircraft and Dispatch was unaware of the weight and balance discrepancy.
Date: 201812
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: Commercial Fixed Wing
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Elevator Trim System
Component problem: Failed
Reporter function: Captain; Pilot Not Flying
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The First Officer was flying on the leg from ZZZ. On the climbout from ZZZ; PTRIM main inop and PTRIM backup inop warnings illuminated. We continued the climb; finished the After Takeoff Checklist and then ran the QRH. The QRH led us to the cutouts for both trims. When we selected the backup trim the warning disappeared and I quickly tried to trim down but it stopped and the warning illuminated again. I finished the QRH; which suggested to consider nearest suitable airport. We discussed continuing to [destination] and continued our climb. We reached level off altitude and as the airspeed increased it became apparent that continuing at normal speed to [destination] would be a difficult task. The First Officer then pulled the power back to help alleviate some of the pressure. As I was trying to formulate a plan and decide our next step; I noticed the First Officer having trouble holding altitude level; I advised the First Officer we were high; he started the correction. At this time; we considered airports nearby and ZZZ1 was directly in front of us. I [told] ATC that we had a control malfunction and were correcting altitude. We [advised ATC] and got direct ZZZ1. I decided to swap controls to give the First Officer a break and because I wanted to be able to feel the control inputs. At our altitude; it seemed ZZZ1 would make a good choice and give us time to run checklists. The timing worked out well and we landed safely at ZZZ1 with no further issues. PTRIM main and PTRIM backup warning messages; plus the inability to control pitch trim.




Synopsis: Air carrier Captain reported pitch trim failure with limited controllability.
Date: 201209
Local time of day: 0601-1200
Location: L18.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: Grumman American Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class E ZLA
ATC / advisory: CTAF L18
Second aircraft: Skyhawk 172/Cutlass 172
Aircraft component: VHF
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Conflict NMAC
Detector: Person Flight Crew
Result: Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: [I was] flying a practice GPS approach to Runway 18 at L18. [I] heard a Cessna 172 aircraft in pattern. Pilot was announcing position on CTAF; but not every leg of the pattern. I was proceeding straight in and announced my position at 10; 5; 3; and 1 miles relative to a straight in final. Was looking for the C172 but did not have them visually. I picked up relative movement in my peripheral vision and saw the C172 in the turn from left base to final at my altitude. They were about 200 FT in front of me but my speed was 90 KTS; much faster than their speed. As we were both descending I made a hard right climbing turn to avoid contact. As I climbed out I called to ask if they had in fact been broadcasting their position the whole time while in the pattern. No response. Upon further investigation it appears that my #1 comm radio; which was in use at the time; is cutting out after I transmit. It returns to normal after several seconds. This transmit problem seems to be happening intermittently therefore make it difficult to diagnose. I have service scheduled for this unit.




Synopsis: GA7 pilot reports a NMAC at L18 during a practice GPS approach to Runway 18. A C172 was heard in the pattern on CTAF but was apparently not announcing each leg so the reporter was not aware of his position until coming into very close proximity. It turns out the reporter's radio was malfunctioning.
Date: 201703
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke; 6
Light: Dusk
Aircraft: Cheetah; Tiger; Traveler AA5 Series
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Electrical Power
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Training / Qualification; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Landing Without Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: Total electrical failure on initial approach.  Landed in VMC without radios or flaps. I did not see any light signals from the tower when entering the landing traffic pattern. After landing; airport personnel asked me to contact the tower. I complied and called the tower by telephone prior to leaving the airport.




Synopsis: Grumman AA5A pilot reported landing without ATC radio contact or light gun signals after experiencing complete electrical failure during approach.
Date: 201309
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: Dash 8-300
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: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Workload; Physiological - Other
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After reaching our cruise altitude of FL190; both the Captain and I felt a sharp pressure change; we noted that the cabin altitude was increasing rapidly. We then executed the required loss of cabin pressure procedures. ATC was notified of our descent and a new altitude clearance was issued. After reaching a safe altitude; we contacted Dispatch Control and determined it best to continue to the destination airport. The flight was completed without further incident.




Synopsis: A DHC-8-300 began loosing pressurization at FL190; so the crew declared an emergency; began a descent; completed the QRH and continued to the filed destination.
Date: 201501
Local time of day: 1201-1800
Weather elements / visibility: Icing
Light: Dusk
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: Flight Crew Took Evasive Action
Contributing factors: Weather; Environment - Non Weather Related; Equipment / Tooling; Procedure
Primary problem: Procedure

Narrative: Jetway gap too big. Arrived at the gate. The Agent opened the aircraft door and I noticed a large gap about 4-5 inches between the jetway and the aircraft and ice on the rubber part of the jetway. I told the agent that the gap was too big and was unsafe for deplaning and that they would have to adjust the jetway. Agent responded with; 'I have moved the jetway twice and that was the best [I] could get it.'I asked the Captain to look at the gap and he responded; if the Agent thinks it's OK then that's fine. The Agent went back up into the terminal. Near the end of deplaning 2 young children walked off the plane with their parents. The young boy turned around and tried to walk back on the plane. He slid on the rubber part of the jetway and slid down between the aircraft and jetway. The father quickly turned around and grabbed the little boy by his jacket and pulled him back up.




Synopsis: An A319 Flight Attendant observed an excessive gap between the aircraft which the Gate failed to close. A young boy slipped on the icy rubber boot and was caught by his father before he fell through.
Date: 201602
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
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: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Diverted; Flight Crew Inflight Shutdown; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Enroute we received a RH OIL PRESSURE master warning message. I was the flying pilot and First Officer ran the QRH for the warning. The oil temp was in the normal range but the oil pressure was fluctuating from 50-25 PSI. The left side was around 70 PSI. After running the QRH for the low oil pressure message we were directed to perform the intentional shutdown of the right engine since the oil pressure was continuing to slowly drop lower. We advised ATC of the situation and that we would be diverting to [a nearby alternate]; since it was the closest usable airport. After advising the flight attendant; passengers and company of the situation we requested vectors to the longest runway available and asked to have emergency equipment standing by just in case. We landed single engine without further incident.




Synopsis: CRJ-200 Captain reported an inflight shutdown of right hand engine after receiving a low oil pressure warning message.
Date: 202107
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: clear; 10
Light: Daylight
Aircraft: Stearman
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Descent
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Distraction; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was scheduled to fly over an event on the coast of ZZZ. I arrived about 20 minutes early and began orbiting nearby. The visibility was excellent and the air was smooth. I could see the mountains in the distance and the pier about 8 miles to the southeast. Rather than continuing to orbit; I decided to fly along the coast past the pier and back. I visually cleared the route from my location to the pier and turned on course; level at 1;200 feet MSL. I began a shallow descent off shore. As I descended through about 800 feet; suddenly; there appeared a banner tow aircraft just barely above and slightly to the left. I pushed down and to the right narrowly avoiding a midair collision.After the event; I realized that I had made a mistake. Even though I had visually cleared the area in front of me; I should not have flown a shallow; wings level; straight-ahead descent. I should have made one (or more) S-turns during the descent to scan for traffic ahead and below my flight path.




Synopsis: Pilot reported a near mid air collision and took evasive action.
Date: 201503
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 7
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Tail Wheel
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Initially aircraft bounced upon landing. Power was added and a smooth touchdown of the main landing gear was accomplished. On landing rollout as the tail settled; a grinding noise was heard. Differential braking was initially effective; but eventually; the aircraft ground-looped hard to the right and the landing gear collapsed; causing the propeller to strike the ground and stopping the engine. Upon disembarking the aircraft; I looked and found that the tailwheel had departed the aircraft. The tailwheel was found on the runway near the point of the initial touchdown. No injuries were sustained by anyone during the course of these events. Upon further examination; the tailwheel was found to have had a faulty weld that lacked penetration. There was no documentation found of any previous repairs having been made to that portion of the aircraft. Improper and/or undocumented repairs under previous owner(s) of this aircraft were a primary factor in the incident.




Synopsis: Pilot of a tailwheel aircraft experiences a bounced landing followed by a smooth landing until the tail is lowered to the runway. A grinding noise is heard followed by a ground loop resulting in gear collapse and a propeller strike.
Date: 202009
Local time of day: 1201-1800
Location: ZAN.ARTCC, AK
Weather elements / visibility: 10
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Final Approach
Airspace: Class E ZAN
ATC / advisory: Center ZAN
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: Other On Approach
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: ZZZ to WRG with 6000 overcast weather 10 miles visibility. Flew a visual pattern to runway 10 WRG at intersection JAXIS with flaps and gear down in the landing configuration. I got a hard terrain warning with all terrain and runway in sight on a visual approach following the track of the RNP 10 WRG. I must have been lower and a 1/2 dot or so west of the RNP approach course. And this is the first time I've flown this approach since the approaches have been updated in WRG; so that warning I got surprised me.




Synopsis: Pilot reported terrain warning on approach.
Date: 201309
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Dash 8-100
Operator: Air Carrier
Mission: Passenger
Flight phase: Other Rejected Takeoff
ATC / advisory: Tower ZZZ
Aircraft component: Propeller Autofeather System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff; General Maintenance Action
Contributing factors: Procedure; Aircraft
Primary problem: Aircraft

Narrative: While on the takeoff roll; the Autofeather System failed to remain armed and as a result I had to call 'Reject; Reject' and we then rejected the takeoff. The Captain then taxied clear of the runway; I made calls to ATC; the passengers; the Flight Attendant; Operations and finally Dispatch. We then proceeded back to the gate and swapped aircraft. While on the takeoff roll everything checked out fine. Then I noticed the auto-feather 'ARMED' light extinguish and called for a reject.I can think of two possible reasons why: First of all; this aircraft has a history of issues with the autofeather system. Second; Maintenance had worked on the Autofeather System the day prior which indicates there may have been improper maintenance.


Second narrative: During the takeoff roll; the First Officer called 'reject' due to the Autofeathering System failing to remain armed before V1. I slowed the aircraft down and took a high speed taxi exit while the First Officer notified ATC. Everyone; including the Flight Attendant; passengers; Operations; Dispatch; and Maintenance were notified and we returned to the gate without any further disruption to the flight and safety. I am uncertain why the system failed to remain armed because I did conduct an Autofeather Test and an Advisory Lights Test before the flight; so I suspect improper maintenance correction or simply equipment malfunction because the Autofeathing System had a recent history of problems. Moreover; MEL 61-2 relief was recently applied to the aircraft.


Synopsis: DHC-100 flight crew reports a rejected takeoff when the Autofeather armed light extinguishes during the takeoff roll.
Date: 201207
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: M-7
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Ground Excursion Runway; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: On landing; aircraft departed to side of an unimproved strip; went through a few feet of a corn field; and then returned to runway. The aircraft was inspected for damage; with only a minor dent on the underside of the airframe. Engine cowl was removed and engine inspected for foreign objects. No propeller damage was noted; and leaves; etc; were removed from around the engine. Then took off and flew the aircraft back to home base. Although the aircraft flew ok; in hindsight; I should have grounded the aircraft until a more thorough inspection of the aircraft could have been accomplished by a qualified A&P.




Synopsis: Maule pilot reports a runway excursion into a corn field during landing at an unimproved strip. The aircraft is inspected and leaves removed from the cowling then flown back to home base.
Date: 201506
Location: ZZZ.Airport, US
Aircraft: B737-900
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Ramp
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Aircraft; Company Policy
Primary problem: Company Policy

Narrative: [We] received a call from [operations] warning us of the risk of tail tip on arrival of [a] B737-900ER. We were directed to offload 20 bags from the rear of the aircraft which had 88 bags and 182 lbs of freight loaded. The forward compartment had 59 bags and approximately 1400 lbs of airmail and 1 dog.  Load Planning should not be planning so much weight to be loaded in the rear of these aircraft. They know these airplanes are tail heavy and yet they keep dictating the load plan to be completed in an unsafe manner putting our aircraft; equipment; employees and passengers at risk.  We offloaded everything from the rear before deplaning any passengers and we still saw a significant weight shift once passengers began deplaning.




Synopsis: Ramp worker reported a 'significant weight shift' during passenger disembarkation in a B737-900ER even though they had already unloaded considerable weight from rear pits.