elihoole/asrs-aviation-reports huggingface dataset:
Date: 201901
Location: ZZZ.Airport, US
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Escape Slide
Reporter function: Flight Attendant (On Duty)
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Pre-flight
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: L1 Door aft-most stowage hook on the slide-bustle was so loose that the girt bar didn't snap into place and was easily lifted out of the bracket with zero force. I notified the Captain who called ZZZ [Maintenance].When [Maintenance] arrived; I said 'Good Evening' but he ignored me. The Captain said the same and [Maintenance] responded 'Is it in the book?' No acknowledgment of our greetings (he didn't even make eye-contact with me).The Captain told [Maintenance] that there was something wrong with his Flight Deck seat; and also the stowage hook on the L1 door. I showed him the door; and he spoke over me while talking to say it was fine. He bent down; grabbed the girt bar from the hooks (far too easily and proving my entire concern) and then put it back in. He looked at the Captain and stated 'It's fine; it doesn't need to be fixed.' I attempted to explain that it should be like the stowage hooks on R1 but again he interrupted me to say 'It's fine.' It didn't get fixed.As an Inflight Instructor; we teach the flight attendants to report anything that's not working properly and for several years have focused on the girt bar stowage hooks in an effort to curtail inadvertent slide deployments or partial deployments. This incident with [Maintenance] was not isolated but it was concerning due to the dismissive and argumentative nature of the mechanic in question. By being disrespectful to and dismissive of ANY employee with a safety concern; it creates a culture whereby we do not want to report anything as broken; we question ourselves; or knowing we won't be taken seriously we simply stay quiet. This needs to be addressed as it is prevalent.Nobody should have to feel belittled or demeaned or worst of all UNHEARD when it comes to safety and if I can't trust [Maintenance] to do their job; then how does that translate to our overall safety culture?




Synopsis: Air carrier Flight Attendant reported Maintenance Technician did not appropriately communicate and evaluate the door slide issue identified by the crew.
Date: 201710
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Beechcraft Single Piston Undifferentiated or Other Model
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Conflict Ground Conflict; Critical; 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: On my first solo landing; as I was on final; and even after I had been making my base and final calls; a Bonanza pulled out onto the runway to takeoff; forcing me to go around. I went into the upwind; and the bonanza did a right turn out; forcing me to do a midfield cross; and his only call was 'Bonanza clear of airport.' I came back in for landing without incident.




Synopsis: A student pilot reported that another aircraft entered the non-towered runway without notice; causing a go around; then performed an early turn; resulting in an airborne conflict.
Date: 201505
Local time of day: 1201-1800
Location: STS.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 6
Light: Daylight
Aircraft: M-20 F Executive 21
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
ATC / advisory: Tower STS
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Confusion
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Airport; Chart Or Publication; Procedure; Human Factors
Primary problem: Ambiguous

Narrative: I received Taxi clearance from STS Ground to Runway 14 at A2. I repeated the clearance - I believe no hold short instructions were given to me. I was at the Z apron and confirmed with STS ground that I can go to A5; then A northbound to Runway 14. I used airport diagram on iPad for Taxi showing Taxiway A passing by threshold Runway 20 but not intersecting it!Upon passing by it and stopping on A2 (holding short of Runway 14); I was told by STS Ground I passed the threshold Runway 20. I believe no incursion occurred and don't remember any marks on Taxiway A prompting me to stop; but I believe it could be a possibly dangerous situation if plane was landing and pilot relying on airport diagram which shows Taxiway A not crossing Runway 20.

Callback: The reporter cannot recall any hold bars on Taxiway A for Runway 20 but states that they may exist and he just was not looking for them.



Synopsis: M20 pilot reports being cleared to taxi via Taxiway A at STS and hold short of Runway 14 at A2. Once holding short at A2 he is admonished by the Tower for crossing the extended center line of Runway 20 without a clearance to do so.
Date: 201509
Local time of day: 0601-1200
Location: MUE.Airport, HI
Flight conditions: VMC
Light: Dawn
Aircraft: Commercial Fixed Wing
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class G HCF
ATC / advisory: CTAF MUE
Reporter organization: Air Taxi
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: Other Takeoff Roll
Result: General Maintenance Action
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Environment - Non Weather Related

Narrative: We were on the takeoff roll from runway 04 at PHMU. At or just before rotation speed of 70 knots; I saw something small and black go straight over the aircraft.  I thought we had just barely missed whatever it was. The captain I was flying with said it was a bird and it had gone through the propeller. I didn't see it go through the propeller; and neither of us felt a 'thud' or any sort of impact from the bird.  All of our engine instruments were reading normal; there were no unusual vibrations from the propeller; and none of our avionics or radios had gone offline. Although we were no more than a couple miles from the airport and a thousand feet or so in altitude; we elected to continue to our destination.The flight continued uneventfully. Upon arrival; we discovered some residue from the bird that we had hit on a four inch section of one of the propeller blades.  That was the only evidence that we had of a bird strike; and the plane took no damage elsewhere. The propeller blade suffered nothing more than a few smears; and maintenance quickly inspected and returned the aircraft to service.In hindsight; our decision to continue was unsafe. We had no idea if or how much damage the aircraft had taken; if it had taken any at all. We were close to the airport and could have easily returned for landing. There is no maintenance base; though; but that is no excuse to [not] land there. And since we were just rotating as the bird struck; I could have called to abort the takeoff; as we had more than enough runway available to stop the aircraft. Both of our decision making was hindered that day; as we were both tired and had already started the flight catching errors.




Synopsis: An air taxi aircraft struck a bird on the takeoff roll from PHMU and continued to their destination where Maintenance found bird strike evidence on one of the propeller blades.
Date: 201506
Local time of day: 0601-1200
Location: IAH.Airport, TX
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B IAH
ATC / advisory: TRACON I90
Second aircraft: B767-300 and 300 ER
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: On the LINNK1 arrival to IAH. We were direct to DENTO and [at] 3000 MSL and about 10 nm from DENTO we encountered wake turbulence. It was so bad the autopilot disengaged. The captain was guarding the controls and was able to regain control of the plane. I asked the controller what we were following and we were behind a B767-300. We reported the wake turbulence event to the controller. Encountering wake turbulence when following a heavy with more than standard separation.




Synopsis: EMB-145LR First Officer reported encountering wake turbulence on arrival into IAH in trail of a B767-300.
Date: 201710
Local time of day: 0601-1200
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-44 Seminole/Turbo Seminole
Operator: FBO
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Taxi
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Distraction; Situational Awareness; Troubleshooting
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Excursion Taxiway
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Regained Aircraft Control
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: While taxiing I momentarily lost control of aircraft striking a taxi light.  No injuries to persons in aircraft or on the ground. Causal factor was divided attention due to windshield which kept fogging up after beginning taxi to runway. Corrective action is to stop when windshield begins fogging and discontinue taxi until clear.




Synopsis: PA44 flight instructor reported losing control while taxiing and striking a taxi light due to a distraction.
Date: 201911
Location: RIC.Airport, VA
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C RIC
ATC / advisory: Tower RIC
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight; Routine Inspection
Contributing factors: Chart Or Publication; Human Factors
Primary problem: Chart Or Publication

Narrative: The Jeppesen chart for the ILS to Runway 34 in RIC does not show a PAPI. The runway has had one for several months now.




Synopsis: Air carrier Captain reported PAPI availability was not published on the RIC ILS to Runway 34 approach chart.
Date: 201407
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Aircraft component: Hydraulic System Lines; Connectors; Fittings
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff we had a total failure of the Green Hydraulic System. We performed all emergency procedures related to that system loss.  Performed an emergency landing on the longest runway; stopped; pinned the landing gear and got towed to the gate.  Maintenance found a defective hydraulic line.




Synopsis: A319 Captain experiences a Green System hydraulic failure just after takeoff and declares an emergency. ECAM actions are accomplished and flight returns to the departure airport.
Date: 201404
Local time of day: 1201-1800
Location: XNA.Airport, AR
Weather elements / visibility: Thunderstorm; Turbulence; Windshear
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C XNA
ATC / advisory: TRACON XNA; Tower XNA
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness; Distraction
Second reporter function: Captain; Pilot Not Flying
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Contributing factors: Weather; Procedure
Primary problem: Ambiguous

Narrative: Approach into XNA from the south; cross east of the field; left turn onto left downwind.  Line of thunderstorms moving in from the southwest[with] winds quite strong at pattern altitude.  [We were] attempting to hustle down and get on the ground prior to the storms' arrival.  Approach cleared [us] to 3;000 on downwind.  Got a turn to base and looking cross cockpit to find field; not where I expected [as] we had been blown further out than expected.  Called field in sight; but slow descent as now we were much further out than expected.  Cleared visual approach and armed LOC/GS.  VMC entire time; runway always in sight.  Captain selects FAF altitude; in a slow descent intending to intercept glideslope from below but reached FAF altitude first; but because of winds further out than expected; Tower asked about a low altitude alert; we went up 200 feet and intercepted glideslope and landed visually.


Second narrative: [Report narrative contained no additional information]


Synopsis: An air carrier on approach to XNA Runway 16 was blown away from the runway by an approaching cell while descending on a left base for a visual. ATC issued a low altitude alert after which the crew climbed to the glideslope.
Date: 201912
Local time of day: 0601-1200
Location: SJC.Airport, CA
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class C SJC
ATC / advisory: TRACON NCT
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General Physical Injury / Incapacitation
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: On our flight to SJC during the descent from 8;000 feet to 4;000 feet we were instructed to expedite our descent. We encountered wake turbulence from a B737 on the same path. On the base turn we got a call from the forward Flight Attendant that the aft Flight Attendant hit her head on the R2 exit sign which caused her neck pain and puffiness above her eye. We continued the approach and assessed the Flight Attendant's condition; which required medical attention from professionals. My First Officer notified the Gate Agent to get medical help while I called the Company via Dispatch; Manager; and Chief Pilot to make them aware of the situation. Paramedics did their assessment and decided to take her to a local hospital. This led to a delay on our outbound flight.




Synopsis: EMB-175 Captain reported a Flight Attendant sustained minor injuries following a wake turbulence encounter on arrival into SJC in trail of a B737.
Date: 202010
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class A ZZZ
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Time Pressure; Communication Breakdown; Workload
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition; Flight Crew Executed Go Around / Missed Approach; Flight Crew Diverted
Contributing factors: Environment - Non Weather Related; Human Factors; Aircraft
Primary problem: Aircraft

Narrative: On initial approach into ZZZ at first flap extension the flaps had an asymmetric condition that stopped the flaps between up and 1 degree; the LEDs (Leading Edge Devices) went to the extend position; no roll experienced. Upon noticing the FO elected to level off and follow the approach track and published missed approach. We informed ATC that we were experiencing a flight control problem and that we would be entering holding. We ran the flap trailing edge asymmetry QRH and decided not to land at ZZZ due to the short runway and degraded runway conditions. We then debated on proceeding to ZZZ1 or ZZZ2. We could not proceed to our filed alternate of ZZZ3 due to the increased fuel burn with the LEDs extended. With a quick rough calculation we decided we had enough fuel to proceed to ZZZ2 that had the longest runway. We contacted Dispatch and they concurred on proceeding to ZZZ2. We then climbed to FL190 and cruised at 220 knots IAS. We ran the ALL FLAPS UP QRH and landed at ZZZ2 uneventfully. Dispatch tried to call Operations Manager but he was dealing with another call.[I suggest] maybe dedicating someone else to 'COVID' situations that took Operations Manager away from being able to assist us. Also having tanked fuel was great because it gave us the option to go to a long runway.




Synopsis: Air carrier Captain reported the Operations Manager was unable to help the crew during an in-flight mechanical problem due to being involved with a COVID-19 situation.
Date: 201510
Local time of day: 1801-2400
Location: A80.TRACON, GA
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ATL
ATC / advisory: TRACON A80
Second aircraft: B737-800
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Separated Traffic
Contributing factors: Procedure; ATC Equipment / Nav Facility / Buildings; Human Factors
Primary problem: Human Factors

Narrative: Operating on a west operation running triple ILS approaches. The localizer for 27L is OTS. So; we were running ILS's to runways 26R; 27R side step 27L; and 28. A B777 requested the RNAV PRM 27L approach and it was approved by the supervisor on the wall. Since we are only able to monitor a total of three finals at any given time it would be required to get another person to monitor the B777 aircraft on a separate scope. Therefore the B777 was not monitored by an appropriate monitor controller for a PRM approach while a B737 was turned onto the Runway 28 final for an ILS PRM approach as well. Separation was lost when the B777 descended below 4;000 feet on the approach. When the final monitors questioned the operation to the supervisor they were told not to worry about it. In turn allowing the separation loss to occur. There was then another aircraft that was going to do the same procedure as the B777; but this time the finals were instructed to stagger so the monitors would not be 'gigged with the error'. It is common practice to staff another monitor controller for such an operation. But in this case it was not followed. Staffing levels may have contributed to this situation and the inability to get personnel in position to run the proper operation required for this procedure.




Synopsis: A80 Controller describes a deviation from standard procedures during ILS PRM approaches to Runways 26R; 27R side step 27L;and 28 when a B777 crew requests an RNAV PRM 27L approach and is approved. There is no one to monitor this approach and separation is lost when the B777 descends below 4;000 feet. When the final monitors questioned the operation to the Supervisor they were told not to worry about it.
Date: 201212
Local time of day: 1801-2400
Location: ATL.Airport, GA
Flight conditions: Mixed
Weather elements / visibility: Rain
Aircraft: MD-88
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class B ATL
ATC / advisory: Tower ATL
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Deviation - Track / Heading All Types; Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; Flight Crew Returned To Clearance
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Shortly after takeoff; we encountered fairly significant wake turbulence from the aircraft in front of us. While recovering from this we turned on course. As we began our turn on the departure; we were queried by ATC to see if we were turning to the fix. We acknowledged that we were and ATC said okay. At no time did I think that we had exceeded any lateral boundaries of the departure and never did ATC mention to us that we had.




Synopsis: MD88 Captain reported encountering wake vortex on departure from ATL that possibly resulted in a track deviation.