elihoole/asrs-aviation-reports huggingface dataset:
Date: 201810
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Company Policy
Primary problem: Company Policy

Narrative: There are several flights leaving ZZZ nightly that have similar sounding call signs. [They are] close enough where flights are taking someone else radio calls. ATC is also confusing them. The same controller runs Clearance Delivery; Ground Control; Tower; and Departure Control. While rolling down the runway for takeoff; it's distracting to hear the Tower giving a clearance to someone that's using a call sign that's very close to ours.  Not only distracting; but [it is] a safety issue.Callsigns that are similar sounding is not new; but I feel we really need to consider changing some of the ones that are close. To use the reasoning that 'this series of numbers are inbound to [certain cities] or outbound from [certain airports]' is not a good reason.  It's also very easy to 'just listen closer' when we're sitting around a table reviewing a report or even flying during daylight hours. After being up all night; it's a possible dangerous pitfall that doesn't need to be there.




Synopsis: Air carrier Captain reported the amount of similar sounding callsigns is a safety concern and a distraction.
Date: 201810
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
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 Security; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: On our flight from ZZZ I was standing outside the flight deck during boarding. A woman who was pre-boarding with a small tricycle style wheelchair reached down and hastily grabbed the battery from the chair before taking her seat. It caught my attention because the battery looked worse for wear. It caused me to reference the FOM. Our concern was whether or not it was approved for the cabin. I then went up and checked with the Ops Agent to see if he had any information on the battery that we were unaware of. He had no idea. He had no idea that there might be a problem. Upon returning to the flight deck the Flight Attendant politely asked if we could inspect the battery; and the woman complied. On inspection; the battery did have the proper sticker indicating it was approved for the cabin; however; barely readable. Upon further inspection; both the positive and negative cables on the pigtail were damaged with exposed wires on both in very close proximity to each other. We then worked with the Ground Ops Supervisor to secure the battery and made safe for transport. Upon landing in ZZZ1 I informed the woman of our rules for carriage; as per the [hazmat] manual; and emphasized the potential danger to the aircraft and to herself if those wire were to short against each other when the chair was in use. She was receptive; with a grateful attitude. Preventative Measures: That had the potential to be a very serious inflight emergency. I believe Ops Agents and Flight Attendants need to be made aware of the danger of large lithium ion batteries such as this; and bring awareness to flight crews of where this information is because we had to dig around a little causing a delay in push.




Synopsis: B737-700 Captain reported passenger boarded with Lithium Ion battery incorrectly packaged for transport. Ground personnel were not aware of the HAZMAT battery safety procedure.
Date: 201902
Local time of day: 1201-1800
Location: CXY.Airport, PA
Flight conditions: IMC
Weather elements / visibility: Icing; Rain; 1
Light: Dusk
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Final Approach
Airspace: Class D CXY
ATC / advisory: Tower CXY
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Weather
Primary problem: Weather

Narrative: Filed IFR for an instrument training flight. During weather briefing no reports of icing or potential icing were seen on 1800wxbrief.com. Departed from ZZZ in VMC conditions; but entered IMC at cruising altitude of 4;000 feet MSL. Temperature at 4;000 feet was +2 degrees C. The winds aloft; checked via ADDS (Aviation Digital Data Service); had forecast +2 degrees C up to 6;000 feet. Descending into destination airport (CXY) started picking up ice after descending through 3;000 feet while being vectored for the ILS approach to Runway 8 at CXY. Despite defrost being set at max; the windshield iced over. Approaching minimums I was focused on trying to sight the runway and approach lights and my student diverted his attention from the ILS display to the windshield as well; resulting in a low altitude alert from the Control Tower. While descending through 1;000 feet MSL the ice began melting. Surface temperature was +1 degrees C. As there was an apparent temperature inversion; decided to check latest weather via ADDS and saw that temperature at CXY and at planned [cruising] altitude (5;000 feet MSL) was positive. Conducted return flight to ZZZ and briefly picked up light icing while climbing through 2;000-3;000 feet. At cruise altitude OAT showed +2 degrees and there was no icing for the return flight beyond the climb-out phase.




Synopsis: PA-28 flight instructor reported encountering unexpected icing during IFR training flight.
Date: 201710
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Propeller Spinner
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Distraction; Confusion
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was level at 3000 ft in cruise configuration when an enormous vibration started. I closed the throttle to minimize the vibration and [advised ATC]. Even at idle; the vibration was so bad that I worried that the engine was going to be ripped off of the airframe. I didn't know the cause of the vibration. I supposed that something in the engine had failed. ATC was helping me find a private grass strip. But I never did see [it] and ended up selecting a soybean field. Once I was sure I had the field made; I switched the mags off. The prop came to a stop and I could see the damage to the tip of the prop. The landing was smooth with no damage to the airplane or anything on the ground. After I got out of the airplane; I could see that the spinner and its mounting bracket had been ripped off also (the mounting lugs of the bracket were still under the prop bolts).




Synopsis: GA pilot reported an off field landing after the propeller spinner and backing plate failed in flight.
Date: 201310
Local time of day: 0601-1200
Location: ZFW.ARTCC, TX
Flight conditions: IMC
Weather elements / visibility: Turbulence; solid cumulus
Light: Daylight
Aircraft: PA-24 Comanche
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZFW
ATC / advisory: Center ZFW
Aircraft component: Altitude Hold/Capture
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Distraction; Human-Machine Interface
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Weather; Aircraft
Primary problem: Human Factors

Narrative: While cruising IMC in light turbulence at assigned altitude 10;000 FT; I was called by Center inquiring about my altitude and was told my mode C indicated 10;500 FT. I had been cruising on autopilot with altitude hold; but apparently accidently bumped the altitude hold button on the control wheel while reading the chart on my iPad; disengaging alt hld. The aircraft climbed 500 FT before I and Center noticed it. This aircraft has an S-Tec 50 autopilot with two small momentary push buttons on the left horn of the pilot's control wheel. One is 'A/P Off' and the other is 'Alt Hld On/Off'; and they are identical except for their color. The buttons are unguarded; protrude well above the control horn itself; and are very sensitive to light pressure. There is no audible or visual warning sound when either the A/P or the Alt Hld function is disengaged other than a small annunciator light on the A/P control head (on the instrument panel) extinguishing; and in this aircraft that control head is partially obscured by the control horn and a portable GPS mounted on the control horn. This is not the first time in the last 3 years I have done this; but it is the first time I've deviated more than 200 FT from my assigned altitude. It was my fault; obviously; and the situation was compounded by the IMC conditions; turbulence; and absence of any significant warning that the altitude hold disengaged. In the past 3 years that I've been flying with these avionics I've become more attuned to this phenomenon; but this time it got away from me.




Synopsis: PA24 pilot reports inadvertent disengagement of the autopilot altitude hold function. The aircraft drifts 500 above assigned altitude before ATC queries the reporter and the deviation is corrected.
Date: 201502
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
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
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Physiological - Other
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency; General Physical Injury / Incapacitation
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During cruise at 33;000 feet in smooth air; a large passenger became ill. The passenger fell in the aisle taking a flight attendant to the ground and breaking her leg in three places. The actions of the other three flight attendants plus an RN; and an EMT trainee resulted in a stabilized situation but necessitating a return to the departure airport. Our contract medical service was advised through our Dispatcher and emergency authority was used in an expedited arrival into the airport where the plane was met at the gate by emergency medical personnel.




Synopsis: A large passenger fell in a B737 isle taking flight attendant to the floor and breaking her leg in three places.
Date: 201406
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Weather elements / visibility: Windshear
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Ferry / Re-Positioning
Flight phase: Landing
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: ATC Equipment / Nav Facility / Buildings; Human Factors; Airport
Primary problem: Ambiguous

Narrative: While on landing approach to Runway 18; stabilized; on glide path according to VASI and AOA [Angle Of Attack] indication in the green I encountered a downdraft [which increased my] descent rate. I applied full power; but could not prevent an impact in front of the runway overrun. The right main gear departed and the nose-wheel collapsed. The airplane slowly nosed over and came to rest inverted. I opened the door and departed the airplane.I had received local WX information from a close by airport; which reported winds 080 to 270/7 G12 KTS; rolling out on final; I noticed a requirement for crosswind correction to the right. I used the low wing method to make sure; I had sufficient control reserve available.Local pilots explained to me; that the glideslope was set non standard to 3.7 degrees and the drop off in front of Runway 18; frequently produced downdrafts. I was looking for the windsock but did not see it on approach.




Synopsis: The pilot of a LSA CTSW failed to account for a steep VASI GS and the potential for downdrafts over the threshold of an elevated runway and was unable to recover from an increase of rate of descent nearing touchdown despite adding full power. The right main departed and the nose gear collapsed causing the aircraft to roll over and come to rest inverted. The reporter exited safely.
Date: 201903
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Second reporter function: Captain; Pilot Flying
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon descending into ZZZ; the lead FA noticed an odor and asked the cabin crew that also took note of the fume. Upon landing I quickly deplaned and was not aware. Upon returning to the plane I also sensed the strong fume mostly in the middle cabin but it migrated to the entire plane and cockpit. The lead FA was visibly ill. I developed a stomach ache was not sure of the cause. We had paramedics check us and my blood pressure was very elevated. I chose to not go to the emergency room. Now I am losing my voice and have lung irritation and coughing. I will be following up with a doctor. Our Captain did not seem affected.


Second narrative: Upon deplaning at ZZZ I was contacted by my lead Flight Attendant about a possible fume event. He related that it occurred during descent which prompted him to contact the flight attendants in the rear of the aircraft. They did not detect anything and he said the fumes appeared to dissipate. While at the gate the fumes/odor escalated and I subsequently contacted Maintenance and my company operations. While I did not personally observe or sense the fumes; it was confirmed by my First Officer; a station manager and numerous ground personnel. After hearing that two of my flight attendants had adverse reactions and my First Officer was not feeling 100 percent; I summoned medical personnel to attend to my crew. After a couple of hours and in coordination with IOC duty pilots and a ZZZ1 Chief Pilot; and after I was assured that my crew was feeling better we left to go to the hotel. Possibly emanating from an air conditioning pack but unsubstantiated.


Synopsis: A320 flight crew reported requesting Maintenance and paramedics after gate arrival due to strong fumes in the cabin and experiencing health issues.
Date: 201711
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Aircraft component: Pneumatic System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During takeoff roll; the Master Caution Light and Bleed Leak Right EICAS message illuminated. Once airborne; other EICAS messages were received and it was determined that the complete right side of the pneumatic system was inoperable. Dispatch and [maintenance] were consulted about the continuation of the flight to the destination. Subsequently; we were advised by ATC that an [aircraft] on the ground reported seeing large pieces of debris falling from behind our aircraft. We were also advised by the Flight Attendants that a loud noise was heard during takeoff. It could not be determined if it was from our aircraft or FOD on the runway. The decision was made to return to [departure airport]. Approach and landing were normal.

Callback: The reporter stated that the flight crew was unaware of what happened; other than the loss of duct pressure for the right hand side. The reporter stated that viewing the damaged area from the ground; it looked like the pneumatic system blew apart internally. The reporter also stated that they were able to see damage inside the air conditioning compartment; including blowing out a section of the fuselage. The reporter stated that the damage to the fuselage did not affect the pressurization of the aircraft. The reporter stated that the air cycle was located forward of the damaged area and could not determine if it was damaged or if it caused the damage.



Synopsis: B777 Captain reported returning to departure airport after the complete right side pneumatic system was determined to be inoperative.
Date: 202103
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: G2 Heritage (Glasair II) / G3 Heritage (Glasair III)
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Other hi speed taxi only
Flight phase: Taxi
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight; Taxi
Result: Flight Crew Became Reoriented; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Owner contacted me to evaluate the aircraft for future flight. The aircraft was looked over; fueled; new battery. After run up; I intended to high speed taxi aircraft on the runway to evaluate engine power. Upon the last taxi the aircraft lifted into the air unintentionally. The engine ran rough upon which I made a teardrop pattern and landed the aircraft; touching down on the grass median between the runway and taxi way. I got onto the runway; taxied to the end and back to the ramp. There was no damage to the airport property or the aircraft. The aircraft was taxied back to the ramp and tied down.




Synopsis: A pilot reported while conducting a high speed taxi for a maintenance check they accidentally became airborne and experienced a rough running engine. The pilot landed off the runway in the grass and but able to taxi back onto the runway.
Date: 201506
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Turbulence; Thunderstorm
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Climbing out at FL190 ECAM alerted us to the fact that our green hydraulic system had low volume; followed by low pressure.  We followed SOP.  Completed QRH and ECAM procedures.  Contacted dispatch with issue who contacted [maintenance].  All agreed to proceed to [destination].  All degraded systems involved landing and taxiing the aircraft.  Took vector to 20 mile final. Completed all QRH; ECAM; and normal ops check lists configured and landed.  Cleared runway on high speed taxiway; with differential braking stopped aircraft and was towed to [gate].Leak in green hydraulic system.




Synopsis: An A320 Captain reported loss of green hydraulic system during the climbout. The Flight continued to the destination.