elihoole/asrs-aviation-reports huggingface dataset:
Date: 201509
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Daylight
Aircraft: Chancellor 414A / C414
Operator: Air Taxi
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Initial Approach
Airspace: Class E ZZZ
Aircraft component: GPS & Other Satellite Navigation
Component problem: Improperly Operated
Reporter organization: Air Taxi
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting; Human-Machine Interface; Distraction; Confusion; Situational Awareness
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 Became Reoriented
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While training for a Checkride; we attempted to execute the RNAV 17 Approach. We discovered that on the last Database update from Jeppesen; both the GPS approaches for our airport; RNAV(GPS) 17 & RNAV(GPS) 34 had been deleted. There was no notification via Jeppesen Update or NOTAM that these approaches were not available. Had this been an IFR/IMC arrival; we would have been caught unaware and would not have been able to land at the destination since the only other approach is a VOR/DME and at the time; the VOR was NOTAMed OTS. This has happened to this operator several times to different airports in the last year. Something needs to be done to notify operators when approaches have been deleted from Databases and subsequently made unavailable.




Synopsis: An air taxi crew on a training flight discovered some airport RNAV GPS approaches in the aircraft GPS database had been removed without notice from Jeppesen.
Date: 201911
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: System Monitor: Indicating and Warning
Component problem: Malfunctioning
Reporter organization: Air Carrier
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: Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Right after takeoff we had multiple system failures; to include the A/T (Autothrottles); VNAV; the Captain's F/D (Flight Director); and the autopilot. We continued the departure and assessed the situation while I hand flew the airplane. I reselected the A/T and they stayed on until I noticed they were not at climb power; but had pulled back to approximately 80 percent. I turned off the auto throttles and pushed up the power; then gave the airplane to the FO (First Officer); whose navigation systems seemed to be working. I advised ATC we needed to return to ZZZ because of the problem. ATC eventually [provided priority handling] for us. While the FO was flying on autopilot I noticed the left engine only had been retarded to 70 percent by the A/T. We turned them back on seeing that everything on his side was working. At this point I took the airplane back and hand flew the plane with F/D; A/T and VNAV off. We were 20;000 lbs over weight so I flew a flaps 40 landing to lower the approach speed. I made a smooth landing and we required no further assistance. We made the appropriate log book entries.




Synopsis: B737 NG Captain reported an in-flight turnback after multiple system failures.
Date: 202110
Local time of day: 0601-1200
Location: OBE.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Initial Climb
Airspace: Class G OBE
ATC / advisory: CTAF OBE
Second aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were taking off at OBE Runway 32; when we were climbing about 200 feet we saw on the GPS that we had traffic coming inbound direct to crosswind at 1;000 feet (that's not a normal procedure to enter on an uncontrolled airport) and he didn't report all the steps he was doing. We report our position in the airport's CTAF to verify he was on the frequency and he was; then he answered 'Affirmative' after that we kept climbing until about 500 feet then leveled up because of the traffic and asked him what he was doing and he answered 'I'm following you' he crossed above us just within 100 feet vertical distance.




Synopsis: Pilot reported an NMAC while departing the traffic pattern of non-towered OBE airport when another aircraft entered the pattern using non-standard procedures and not communicating their intentions.
Date: 201511
Local time of day: 1201-1800
Light: Daylight
Aircraft: B787 Dreamliner Undifferentiated or Other Model
Operator: Air Carrier
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Second reporter function: Flight Attendant (On Duty)
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Clear air turbulence that lasted at least 15-20 minutes.  The problem with the 787 is that there are only three jumpseats in the back of the aircraft.  There were 5 Flight Attendants in the galley when we hit turbulence and not enough jumpseats. We immediately sat on the floor. Where I was sitting on the floor there wasn't even anything that I could hold onto.  I feel the airlines should either install more jumpseats or block passenger seats near the galley so that there is somewhere to sit when turbulence occurs.


Second narrative: 45 minutes from landing the aircraft dropped and carts were lifted off floor. I was working in rear galley cleaning up after last service. This was unexpected turbulence. There were no PAs made because this event was unexpected. There was another drop and all 6 FAs in rear galley fell to floor. There are only 3 rear jumpseats on this 787 so 3 FAs including myself had to sit on the floor. There were no restraints to hold on to; nothing to protect us from inserts of trash; coffee; soda and trash falling onto us and the floor. At this point of the flight hot liquids were in coffee makers and it poured out onto several FAs.This 787 needs to have 6 jumpseats in the rear as that is how many work there. This is a safety issue for the FAs. There is nowhere for us to secure ourselves; a serious safety issue!


Synopsis: Two B787 flight attendants reported a clear air turbulence encounter during cruise.  The flight attendants noted there are not enough aft cabin jump seats to go around in the event of turbulence.
Date: 202111
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Workload; Time Pressure; Other / Unknown; Distraction; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object; Ground Event / Encounter Weather / Turbulence; Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach; Flight Crew Regained Aircraft Control
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: On the day of the incident; me and a pilot friend were going to have lunch at ZZZ1. I was pilot flying during the first leg from ZZZ to ZZZ1 and then he was going to fly back. My previous experience in [this aircraft] was in a different model; but since that plane wasn't available we took [this aircraft]. The conditions at the airport were good VFR with a crosswind of about 80 degrees from the right at 8 KTS. On the first attempt to land; I did a go-around because we were not stable. The second approach was good until the flare which was a bit high; we bounced and on the second bounce my friend called for the controls. Since he is the more experienced pilot; I complied. After that we lost control and veered to the left of the runway; he immediately started a go-around; but the flaps were still down. As soon as we noticed we cleaned the aircraft up and took off again. However; in between we ran over the side of the runway and hit a plastic barricade that was on the grass next to the runway. Once in the air again; we performed a low approach to make sure the landing gear was in good condition and landed; this time without incident.




Synopsis: Private Pilot reported two unstable approaches with the second approach resulting in an encounter with a plastic barricade on the side of the runway. After a low approach to check for damage to the aircraft; a landing was accomplished.
Date: 201701
Local time of day: 0601-1200
Location: BDR.Airport, CT
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Reporter function: Observer
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Rotorcraft; Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Glider; Maintenance Powerplant; Maintenance Airframe
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Observer
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Airport; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: This Airport has recently completed major reconstruction of Runway 6-24 with the addition of a Runway Safety Area. Along with the runway reconstruction; Taxiway Alpha was extended to the full length for Runway 24. The work was completed the first week in October; 2016; and the taxiway was finally painted and opened about a month later.The published Airport Diagram has yet to be updated by the FAA. Therefore; the new section of Taxiway Alpha does not appear on any charts. Pilots are often confused about taxi instructions and end up taxiing to the wrong location when issued taxi instructions to Runway 24. Occasionally; aircraft are stopping on the intersecting runway or stopping at Taxiway Hotel. This requires extra coordination by Ground Control and Local Control. This results in extra work for ATC and a safety issue on the Airport. Corrective action seems simple.Additionally; the location of the slightly offset Localizer on Runway 6 was removed from the Approach Charts. We often hear pilots advise the tower that the Localizer looks to be out of calibration. The controller then makes a report that the Localizer might not be correct. Pilots expect the Localizer to be at the end of the runway this Localizer is beside the end of the runway. Having the Localizer placed back on the chart could help alleviate this problem.




Synopsis: A pilot reported that BDR has recently completed extension of Taxiway A and the addition of a runway safety area for the approach end of Runway 24. Reporter stated the Airport Diagram needs to be updated to reflect the modification.
Date: 201907
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 12
Light: Daylight
Aircraft: Vans Aircraft Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Second aircraft: Helicopter
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was approaching ZZZ from the southeast for the purposes of a touch and go landing using the CTAF. At 4 miles I announced my intention; made my position known; saw no other aircraft on my ADS-B; and declared a right base for a 3 mile final for runway XX. Noting no other communication referencing ZZZ; but hearing radio traffic at [other airports in the vicinity]; I made the decision to continue with my landing approach - did not see any other aircraft in vicinity. I aligned with the runway and made a position report at 3 miles and again at 1 mile; hearing no other traffic I stabilized for my landing. At about 1500 ft from threshold; I heard a very loud helicopter noise; looked up and a large green chopper was directly above and slightly to the right of me and in descent to land. I dove to the left making a wide sweeping turn to realign with the runway. The helicopter was landing in the center of the runway and stayed there. I called for the aircraft landing at ZZZ but got no response. After some time; I called my position and intention to leave the area. I left the vicinity of the airport toward the southeast (240 degree heading). In retrospect; I should have entered a left crosswind for XX and completed the entire pattern. Using a full pattern would have taken more time and given the other aircraft opportunity to communicate and/or me more time to visually see the approaching helicopter. Additionally; at no time did the helicopter appear on my ADS-B screen (thus; no warning of an impending near miss). The other aircraft not communicating on [CTAF]; was a contributing factor as well as me not being seen by them.




Synopsis: GA pilot reported a NMAC with a military helicopter on short final at non-towered airport.
Date: 202003
Local time of day: 0001-0600
Location: ATL.Airport, GA
Weather elements / visibility: Fog
Aircraft: Heavy Transport
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class E A80
ATC / advisory: TRACON A80; Tower ATL
Reporter function: Observer
Anomaly: ATC Issue All Types
Detector: Person Observer
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: I have been dealing with ATL ATC telling aircraft to fly low over my community for 3 months. I live in Douglasville; GA 25 miles from the airport. My altitude is 1;000 MSL. This happens from XA00 am to XH00 am. Often ATC has passenger jets lower altitude to 4;000 MSL and fly west bound for 10 miles; turn south 5 miles and then start approach into ATL as much as 40 to 50 miles. This is dangerous to passengers and they are doing it to disturb my community. This morning I had Aircraft X fly over and shake my neighborhood at 3;200 MSL at XA00 am; and I took a screen shot. I have made complaint after complaint of this dangerous behavior. Again; my home is already at 1k MSL.  This is unacceptable and Atlanta ATC is not responding to the many noise complaints I have filed.




Synopsis: Individual reported ATL TRACON/Tower has been allegedly clearing Heavy aircraft to fly too low over Douglasville; GA which is located 25 miles from the airport.
Date: 201601
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Aircraft: A321
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: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Distraction; Troubleshooting
Anomaly: Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Diverted; General Physical Injury / Incapacitation
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: When we showed up for our flight our X flight attendant was not there. He ended up arriving 1 1/2 hours past our report time. When he boarded the plane he was very disheveled and mad. He said he was mad at scheduling for giving him the wrong time. He then started to get emotional and cry. He went from angry to crying several times. I assumed he was acting this way because he'd been thrown off from being late. We immediately started boarding and he was at his boarding door. After we took off he started acting more erratic. He was pacing back and forth in the back of the cabin and was acting strange. When we tried to talk to him he wouldn't look at us. He kept unwrapping and chewing gum and then spitting it out and doing it again. He went out to do service with Flight Attendant Y and I did my service in the back of the cabin. After service he came back to the back and sat down on the jump seat. He would go between being passed out and snoring on the jumpseat and then waking up jerking around and saying weird things. He then would jump up and start opening and slamming the carts shut. He was acting crazy. We knew he was on something. The passengers in [rear cabin] started asking us what was going on and if we needed help. Flight Attendant B decided to go talk to the Captain and he decided to land.We enlisted the off duty flight attendant to take over his position and sit in the jumpseat for landing. We also enlisted 2 non-rev passengers who were fairly big to sit with him. He had no idea we were even diverting until after the two other flight attendants; and myself had cleaned up the cabin and secured everything for landing. He was still in the back and was so out of it he thought we were landing [at our destination] until Flight Attendant Y told him he wasn't going to sit in his jumpseat. He got very angry. We landed and the medics came on-board to get him. After he was taken off the plane a passenger told the off duty flight attendant that he had thrown a trash bag in the overhead compartment by his suitcase earlier. She contacted the Captain and he came back and got the bag.




Synopsis: Flight Attendant reported one of her colleagues was late to the flight and acting very emotionally and strange through the flight. The flight diverts to remove the Flight Attendant.
Date: 201708
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 5
Light: Daylight
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Generator Drive
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Approximately one hour prior to descent; Level 2 Gen Drive 3 Fault occurred; accomplished checklist and disconnected. During descent about an hour after disconnecting the IDG; we received multiple level 1 alerts; at the top were; Bus R Emer AC Off and Bus AC 3 Off. All FOs displays and MCDU blank; stick shaker going off and multiple other warnings. We reviewed the level one alerts checklist for these items which doesn't tell you much. We considered using the Level 2; Gen Bus Fault checklist but decided to review the system manual inoperative equipment list for the bus losses. Additionally; we contacted Operations and Maintenance Control for further recommendations. We agreed we could continue to a safe landing. The one issue that concerned us was all of the number one engine fuel pumps would turn off for approximately 1-2 minutes then cycle and do it again. This would give us the warning that it was now suction feeding. We did not have any other notable electrical loss on any other bus. At approximately 200 ft on final both buses came back online. Landing was normal.


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


Synopsis: MD-11 flight crew reported a generator drive fault with multiple alerts. Crew accomplished checklists and landed successfully.
Date: 201703
Local time of day: 1201-1800
Location: ZDV.ARTCC, CO
Flight conditions: VMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: Widebody Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZDV
ATC / advisory: Center ZDV
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Speed All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Weather
Primary problem: Weather

Narrative: During cruise at FL360; approximate location was DEN 304 radial/120 NM; we experienced Severe to Extreme turbulence.  Airspeed initially increased by 25 kts with simultaneous severe turbulence and an approximate 300 FT increase in altitude and a rapid roll to about 20 degrees of bank.  The autopilot disconnected on its own and the airspeed then decayed rapidly by approximately 40 kts to about 20 kts below desired indicated airspeed at which point it may have momentarily entered the lower foot.  I immediately pushed the throttles forward to regain airspeed and hand flew the aircraft while the Captain called ATC for an immediate descent.  We descended to FL340 and regained our desired airspeed in the descent. We exited the severe turbulence about FL350 and once we leveled at FL340 I re-engaged the autopilot. There were no personal injuries. The Captain notified maintenance via ACARS and made an [logbook] entry.




Synopsis: A wide body freight aircraft flight crew reported severe clear air turbulence with a 40 KT airspeed fluctuation; a rapid climb and roll. The crew descended from FL380 and into smooth air at FL340.