elihoole/asrs-aviation-reports huggingface dataset:
Date: 202101
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
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: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate; Routine Inspection
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: At [Gate] at ZZZ; the First Officer said he saw [Package] near the aircraft; I had just received the cargo load report; so I asked the tug driver over the headset if [Package] was loaded onto the aircraft; he said he would double check and asked someone. He got back to us with that there was no [Package] onboard. I also specifically asked about the presence of dry ice (Dangerous Goods); and the answer I got was that there was not. So neither of those were marked on the cargo load sheet; and neither were onboard according the verbal response I received. I assumed it was coming off our aircraft from the previous flight or destined for another flight. The First Officer during the post flight at [Gate1] at ZZZ1 saw [Package] in our cargo compartment waiting to be unloaded. I do not know if there was any dry ice with it.




Synopsis: EMB-175 Captain reported undocumented Hazmat transported due to a communications breakdown between flight crew and Ramp personnel during preflight.
Date: 202103
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Laser
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Green laser event; continued to landing. Still had symptoms the next day but flew one leg as pilot monitoring; ZZZ to ZZZ1. Still having pressure symptoms in left eye.




Synopsis: Pilot reported eye injury after a laser was directed into the cockpit from a ground source.
Date: 201712
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown
Second reporter function: Flight Attendant (On Duty)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; General Physical Injury / Incapacitation
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: After pre-landing service we were securing our galleys when we encountered turbulence. What appeared to start quickly as moderate escalated into SEVERE. Coffee pots were spilling; trays falling out of carts; passengers screaming. The five of us working began yelling for passengers who were waiting for restrooms to HOLD ON! Fasten seat belts! Those passengers couldn't possibly get to their seats because walking was impossible. I tried personally to get from the corner of the galley counter to my cross-aisle jump seat but was unable to do so. I held on to the counter top but the next drop took me almost to the ceiling. The worst turbulence event that I've experienced in years. There was no announcement from the cockpit whatsoever. Seatbelt announcements were made in both English and Portuguese.A medical event followed. [One] passenger seated experienced a full on panic attack. Symptoms progressed to be similar to a petite mal seizure. He was attended to by the doctor while we checked on passengers as turbulence would allow. There was absolutely no contact from our pilots regarding the event or after. No Flight Attendant Check in announcement; No follow up with the crew whatsoever to see how we OR the injured passenger was doing. When asked about it; the event was completely minimized and disregarded. They mentioned that we had to descend through a storm and that 'it happens sometimes'.


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


Synopsis: Two air carrier Flight Attendants reported an encounter with severe turbulence marked by a lack of communication from the flight deck.
Date: 201910
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Aircraft component: Exterior Pax/Crew Door
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued New Clearance; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff; an extremely loud buffeting noise started. I talked to the Flight Attendant and could hear it was much louder in the cabin via the interphone. Flight Attendant said it was coming from the main cabin door. I told the First Officer to level out; we stopped around 6;000 feet. Around that time I noticed the cabin climb rate was 2;500 FPM. I assumed that the door seal had blown. I notified Maintenance and Dispatch that I would be returning to ZZZ. We landed overweight at about 48.6. Landing was extremely light (greased on). We'll guesstimate 01 FPM. No passengers complained of pressure issues.




Synopsis: CRJ-200 Captain reported a pressurization problem during climb that resulted in a return to land.
Date: 201605
Local time of day: 0601-1200
Location: ZTL.ARTCC, GA
Flight conditions: IMC
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZTL
ATC / advisory: Center ZTL
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Training / Qualification; Confusion
Second reporter function: Pilot Flying; First Officer
Anomaly: ATC Issue 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 Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure
Primary problem: Procedure

Narrative: While deviating around weather at FL240; 'PARQR fix when able;' - the ATL CTR clears flight to descend via the PARQR 1 RNAV Arrival landing south. We query that we are not direct PARQR. Controller re-states clearance. We decline; but say once we go direct; we can be cleared to descend via. The two following aircraft get same clearance and have the same disagreement. After the third aircraft; controller says that is how he was trained to do it. The FAA inspector riding with us; agreed with our interpretation and said; if we had left F240; it would have been considered an altitude deviation. Evidently; ATC trains controllers differently from how pilots are trained.


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


Synopsis: An air carrier flight crew deviating for weather was cleared by ZTL to Descend Via the CLT PARQR 1 but refused because the flight was off track and not flying the arrival.
Date: 201209
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Rudder Control System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Technician
Human factors: Troubleshooting; Time Pressure
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
Result: General Maintenance Action
Contributing factors: Procedure; Human Factors; Incorrect / Not Installed / Unavailable Part
Primary problem: Human Factors

Narrative: An Embraer arrived with a scheduled job card for [an operational check of all flight control system power control units]. I started performing the task and the lower rudder PCU failed the check. I notified the hangar and they picked up the aircraft to take to the hangar for PCU change. I discovered that the aircraft [had been in another station the previous night]. Maintenance had deferred this job card with a memo of 'need rudder actuator'. They did not properly defer the task card with maintenance control. They were aware of a failed lower rudder PCU and failed to take the necessary steps to fix it. This means the airplane was illegally flown due to the [known] faulty lower rudder PCU. The part was already requested and stated ensure on hand on the cover page of the task card. Suggestions: If you find something broke; fix it or follow the proper procedures to allow the aircraft to fly legally.




Synopsis: A Maintenance Technician that was assigned to accomplish a maintenance task card discovered that the card had been started at a previous station. The card and the identified defect were not properly addressed and appear to have been flown out of compliance with the maintenance program.
Date: 201307
Location: ZZZZ.Airport, FO
Aircraft: B747-400
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Fuel Storage System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Other / Unknown
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Procedure

Narrative: Doors armed and before pushback fuel started spraying out of the left wing. The fuel was running underneath the aircraft. It took 30 minutes for fire trucks to arrive. In the meantime passengers and crew were becoming very concerned about their safety. The day before this airplane had the same problem and the crew was under the impression that it was fixed. One of the returning passengers saw the leak and insisted on getting off the plane. The jetway came back after the Captain called and he was allowed to get off. With fuel still coming out the other passengers were asking to get off too as fear of the situation started to rise. Passengers started to gather at [door] 2L with their luggage wanting off. Even though announcements were being made by the purser passengers still crowded the aisle with luggage in hand wanting off. Yelling and screaming at 2L started to escalate but the agents said passengers could not get off because they were waiting for officials to arrive. All other doors remained armed since the doors leaving the jetway were locked. In an emergency that would have been our only way out. Finally after quite awhile; not sure of the exact time; passengers were able to get off. The flight did cancel.




Synopsis: Following the discovery that fuel was leaking from the wing of a B747; the cabin crew and passengers became concerned for their safety. The passengers began to become upset when they were not allowed to exit the cabin. Eventually the passengers deplaned without incident.
Date: 202012
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Aircraft: PA-46 Malibu Meridian
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
Aircraft component: Nose Gear
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Rotorcraft; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Flight Instructor; Other Rotorcraft
Human factors: Time Pressure; Situational Awareness; Distraction; Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other landing rollout
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon landing on the centerline of runway at ZZZ the airplane made an uncommanded turn to the left. Even with rudder input and braking I could not keep the airplane on the runway. The left wing clipped the 3;000 ft. remaining sign. Winds were 340 (degrees) at 12 (knots) gusting to 19; (pretty much straight down the runway). Inspection of the airplane showed that during the excursion the nose gear was completely sideways such that the 'Goodyear' was worn off of the sidewall.I do not have 'lazy feet.' I believe that my quick response to the airplanes movements prevented more damage as I was able to stop the airplane just off the runway. I have been flying PA46 airplanes for eleven years including 300+ hours in the Matrix and 1000+ hours in the Meridian/M600.There is no good explanation for the airplane's diversion. Subsequently I found out that there have been 5 other M600s that have experienced no less than 7 similar excursions. I and others believe there is a material problem with the PA46 M600.




Synopsis: PA46 M600 Pilot reported loss of directional control during the landing roll out and exiting the pavement.
Date: 202003
Local time of day: 1201-1800
Location: ASD.Airport, LA
Weather elements / visibility: 50
Aircraft: Sport 19
Operating under: Part 91
Flight plan: None
ATC / advisory: CTAF ASD
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Flight Engineer; Flight Crew Private
Human factors: Situational Awareness
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: Other landing roll
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Environment - Non Weather Related; Human Factors
Primary problem: Airspace Structure

Narrative: Landing at ASD. Wind was reported light and variable. During flight I noticed from ground fires that winds were coming from the east.At approach 3 miles out a parachute jump plane reported jumpers away at 10;000 ft. and below. On final all three of the parachutists had their parachute canopies open and drifting east as expected. On landing two of the parachutes were on the ground; one landing on the parking area east of the drop zone and far way from my aircraft. I was at least 2;500 ft. away from them. The third had somehow steered his parachute over the runway and my only choice was to continue my roll-out because making a go-around would have put my aircraft closer to the parachutist.When I turned off the runway the parachutist had just landed on the edge of the runway and was pulling in his chute. So I am assuming he landed 10 seconds after I passed under him.The drop zone being used at ASD is too close to the runway. The drop zone is actually just to the center of the runway between the taxiway and runway. There is plenty of room at the north or south end of the runway; and [that] would be a safer place for landing parachutes.




Synopsis: Pilot reported passing under a parachutist on his landing roll at ASD airport and suggests relocating the drop zone to a safer area.
Date: 201707
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Weather elements / visibility: Haze / Smoke; 6
Light: Daylight
Aircraft: PA-28R Cherokee Arrow All Series
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Trainee
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Situational Awareness; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Gear Up Landing
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Doing a Flight Review with a flight instructor. The plan was to fly to ZZZ to do one touch and go and one full stop landing (on a very narrow runway) before proceeding to the 'South west practice area'. The distance is about 11 nautical miles; thus a very short flight.  After being advised to go to advisory frequency until flying over ZZZ was less than 2 min. Realizing I was midfield and at pattern altitude I slowed the aircraft down to approach speed and was proceeding with traffic advertisers; and setting up my landing pattern. At this point I should have done GUMP but inadvertently failed to do so. I did a fairly close pattern due to some towers not far from the approach end of runway but as wide as I could to get a good stable approach for what was a very narrow runway relative to my experience. The final approach I became fixated on maintaining precise center line and approach speed to be able to do a short field touch and go. In [doing] this I again failed to GUMP (Gas UNDERCARRIAGE Mixture Prop). I then very nicely landed dead center of the runway just at the touch down point with my gear up.Things that contributed to my not maintaining my normal landing routine.  1) Trying to fly and listen to an instructor (keep a sterile cockpit)2) Not using the GPS to navigate - I always use a GPS and distance tells me when to slow down; GUMP ...3) Focusing on the narrow runway generally at about 200 AGL I will check the gear lights one more time.4)Having transitioned from a [Cessna] right after I got my Private to [Piper Arrow] and doing all my instrument training in it; the VAST majority of my experience in a retractable landing gear is long (10 + miles) straight-ins. Typically I will GUMP 3 or 4 times in during that approach phase.




Synopsis: Piper Arrow pilot reported a gear up landing due to distractions.
Date: 201606
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: Cessna 150
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Engine
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted
Contributing factors: Weather; Human Factors
Primary problem: Human Factors

Narrative: On ferry flight in Cessna 150M. Stopped for fuel. Added 10 gallons after 2.5 hrs flight time. At 3;500 ft MSL engine began running rough. I immediately informed Center that I was diverting to [a nearby airport]. Upon entering downwind I switched to Tower and informed them I was having engine problems and needed to land right away. I was cleared with options for the shorter runway. On short final; engine quit a moment before touch down. With enough [momentum] I taxied to nearest intersection. No further action required from emergency services. Upon receiving a tow to nearest maintenance facility; I determined I ran out of fuel after checking tanks. Added 14 gallons for remaining 10 minute flight.Why this happened: It was a hot day; in an unfamiliar aircraft; running at full bore; with a headwind. Simply; I thought I had enough fuel and I did not. Conclusion: First and last time that will happen. Topping off every chance I get. Increasing personal minimums to no less than 2 hrs fuel on board at all times.




Synopsis: C150 pilot diverted to an alternate when the engine began to run rough due to fuel exhaustion. Engine quit prior to touchdown.
Date: 202006
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew FLC Overrode Automation; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon departure and positive rate climb.  Cycled gear handle to up position.  HYD PRESS light remained illuminated along with the Red Gear Unlocked light.  Proceeded to perform memory items for HYD PRESS light.  Gear extended normally with three green and HYD PRESS light out.  Upon cycling up the second time the HYD PRESS light remained illuminated and the Gear Unlock also remained illuminated.  As I was within 2 miles of ZZZ and still on Tower frequency I called Tower to request a return to the airport informing them of the hydraulic pressure issue.  They then cleared us to land on XXL.  Performed normal approach and soft landing holding the nose off till slow speed.  Proceeded slowly and safely back to the gate.  Tower expedited our return.  Crew did not declare emergency as we received normal gear down indication and we heard Tower inform other company traffic that they were expediting our 'emergency' return.  There were no passenger or crew injuries.  No damage to the aircraft.  No emergency equipment was rolled to my knowledge nor required.




Synopsis: Captain reported landing gear failed to retract after takeoff; causing an air turnback and emergency landing.