elihoole/asrs-aviation-reports huggingface dataset:
Date: 201307
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Beechjet 400
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Flight phase: Cruise
ATC / advisory: Center ZZZ
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Declared Emergency
Contributing factors: Airport; Human Factors; Weather; Procedure
Primary problem: Ambiguous

Narrative: ATC required us to hold over intersection for 40 minutes. After our EFC we were told [our destination airport] was closed indefinitely due to weather. When we checked weather it was VFR. We asked how MMU was and ZZZ1. We were told MMU wasn't an option but ZZZ1 was fine. We were cleared to ZZZ1. When we got to [VOR] we were told to expect holding. We notified ATC that we wouldn't be able to hold the entire time they gave us and that we will need to declare minimum fuel if held for much time. We were then given the hold. [I] and the copilot agreed that when we got to 1200 pounds we would declare min fuel. After one lap in the hold we were at 1;200 pounds of fuel and I declared minimum fuel. We were given a radar vector for the approach into ZZZ1 and we were number two for the airport. Shortly after the radar vector was issued we were told ZZZ1 was closed indefinitely. At this point [all airports in close proximity] were supposedly shut down. We quickly tried to find another option and decided to ask ATC which he told us to divert to ZZZ2. The copilot plugged ZZZ2 into the FMS and it came back saying we would land with twenty pounds of fuel. At this point I also noticed we were at 1;000 pounds of fuel and asked ATC if there was anyway to get into ZZZ1. Answer was no at which point I declared a fuel emergency and need an airport closer than ZZZ2. ATC recommended ZZZ 25 miles away. We agreed that would work and was cleared direct ZZZ. We were given a frequency change at which point we were cleared to another waypoint and then ZZZ. We reminded ATC we had a fuel emergency and that we had the airport in sight. ATC then cleared us for the visual. We landed with no further problems with 700 pounds of fuel on board. Weather at ZZZ1 at XA56Z was reporting winds variable at four knots; 10 SM visibility; clear; 31 degrees C; dew point 22 C; [and] altimeter 29.95. The flight planned time was 2:17 and the actual time was 3:36.




Synopsis: A BE-400XP flight crew had to declare a fuel emergency to obtain a timely approach and landing clearance at their second diversion airport. Both their destination and first diversion airport closed prior to their approach clearance although both were reporting VMC weather.
Date: 201909
Local time of day: 0601-1200
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Aircraft component: Cooling Fan; any cooling fan
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Just after liftoff; the Equipment Cooling Exhaust light came on. As we climbed out; we ran the checklist in the QRH and switched to the alternate fan. After about five minutes; the light was still on. We contacted Dispatch to see if they wanted us to divert or continue to ZZZ. While we were waiting for their answer; we looked up the MEL for both fans being inoperative. MEL has a note about not flying over 30 minutes because of the possibility of losing the First Officer Display Unit and the upper center Display Unit.We also checked the circuit breakers to make sure they were not open. After Dispatch initially wanted us to continue; we diverted to ZZZ1. We were ok with this; considering the amount we were overweight for landing at that point. We did land overweight; but we elected not to burn [excess fuel] because of the additional flight time required to do so. This aircraft had a history of this issue. Both the fan and the sensor had been replaced in recent days. I did not feel comfortable flying internationally in this condition.




Synopsis: B737-700 Captain reported loss of the avionics cooling fan after takeoff that resulted in a diversion.
Date: 201209
Local time of day: 1201-1800
Location: BHM.Airport, AL
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C BHM
ATC / advisory: Tower BHM
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Distraction; Human-Machine Interface
Second reporter function: First Officer
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport; Airspace Structure; Chart Or Publication; Environment - Non Weather Related; Procedure
Primary problem: Procedure

Narrative: [We were] cleared for visual approach to Runway 6 from (approximately) a 6 mile right downwind. [We] flew base over antenna tower. We had excellent visibility and clearly had adequate clearance both horizontally and vertically from antenna. We were well above the 2;200 FT glide slope altitude for the MCDEN final approach fix and descending to join the final approach just inside of MCDEN. We received an obstacle aural warning; possible vertical or horizontal separation from antenna. I suggest either fly a downwind that's not so far from the airport and closer to the final approach than the antenna towers or fly farther out on a longer downwind; turn base outside of the antenna towers and intercept the final approach a few miles outside of the MCDEN final approach fix as would be normally be done in IMC.


Second narrative: On base for Runway 6 into BHM. Clearly had vertical and horizontal separation on obstacles and still got a terrain EGPWS caution.


Synopsis: An Air Carrier crew reported an EGPWS alert from an antenna on a right base to final about six miles from BHM Runway 6.
Date: 201902
Local time of day: 1801-2400
Location: MMGL.TRACON, FO
Flight conditions: VMC
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON MMGL
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Second reporter function: Pilot Flying; Captain
Anomaly: Flight Deck / Cabin / Aircraft Event Other / Unknown; Inflight Event / Encounter Other / Unknown
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: On a right base at approximately 11;000 feet; a bright green laser started trying to lock on to us from the right side (First Officer side); we ducked in the cockpit; which then became fully engulfed in a green light. We were 90 degrees to final [when we] reported laser to ATC; they were busy but said they would send someone out. We were vectored across final due to traffic; made a right turn to intercept and just before final; we were lasered again; possibly from the same location; but not sure; still a green laser. This time; the light came from in front of the aircraft; but slightly from the right of the aircraft and we were at about 10;000 feet. We remained low in the cockpit to avoid being hit with laser until final approach; neither of us were harmed by the event. [We] called dispatch to give a warning.


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


Synopsis: Air carrier flight crew reported being targeted by a green laser.
Date: 202012
Local time of day: 0601-1200
Flight conditions: VMC
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Climb
Airspace: Class E ZZZ
Aircraft component: Elevator Trim System
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After trimming for level flight and while adjusting the prop for cruise; the airplane suddenly started shaking violently at a regular and high frequency. Thinking that something had gone wrong with the prop; I reduced throttle to try to reduce the severity of the shaking; but this had no apparent effect. Engine oil pressure and temperature were both well within the green range. We had just departed a nearby airport; so turned around to land. I noticed that keeping the nose of the airplane up required significant back pressure. Adjusting the trim appeared to have no effect. Enroute to the airport the shaking suddenly stopped. We continued to land without incident. After stopping the airplane on the ground we inspected the trim tab and found that it was stuck in nose-down position. Looking underneath the elevator; we found that the trim-tab control rod was not connected where it usually met the horizontal stabilizer. The end of the trim-tab control rod towards the stabilizer appeared to have been bent and broken. It appeared that at some point the rod broke and jammed. After replacing and reattaching the trim control rod the airplane is operating normally and has been returned to service. Speculation is that at some point the bolt connecting the rod had either partially failed or come loose; causing uneven stress on the control rod; eventually resulting in failure due to metal fatigue. The elevator trim cable had recently been replaced but it is not clear if the control rod had been touched as part of that work. Inspection of this connection point can be done simply and quickly during pre-flight and may benefit from increased awareness as a possible or likely point of failure.




Synopsis: C182 pilot reported severe vibration caused by the elevator trim tab control rod breaking in flight.
Date: 202108
Local time of day: 0601-1200
Location: EWR.Tower, NJ
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
Second aircraft: UAV: Unpiloted Aerial Vehicle
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Distraction; Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Unauthorized Flight Operations (UAS); Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Stadium visual 29 approach to EWR. 2.5 miles south of Meadowlands at 2;300 feet AGL. White plastic swing drone; coaltitude; went under right wingtip. No time for evasive action after sighting.




Synopsis: Air carrier flight crew had a near miss with a UAS while on final approach.
Date: 202101
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise; Descent; Climb; Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Physiological - Other; Situational Awareness; Workload; Communication Breakdown; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate; In-flight; Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Boarding the flight from ZZZ-ZZZ1 half of the passengers on board either had their mask down or half down from their nose. We asked them several times as well as made all the announcements and I notified the Captain and the Gate Agent. The Captain made several announcements after the Agent brought down the flights designated Supervisor. The Supervisor proceeded to make an announcements to please follow the mask policy. They had to follow the company's mask policy or potentially be removed from the flight. Passengers complied but soon after we made a walk through; all the above passengers had their mask off; completely removed and not even visible. I notified the Captain and he told me to the write down seat numbers. Upon arrival he would hand it to the Station Managers. ZZZ1 Supervisors and Gate Agents were informed and said thanks for our great work and professionalism. They will take care of the incident with the Station Manager.




Synopsis: Flight Attendant reported several passengers would not comply with the face mask policy during boarding.
Date: 201603
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Training / Qualification
Second reporter function: Captain
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was the First Officer on Reserve with a shorter than normal call out; and given short term parking and to get there as soon as possible. I made it to the airport with plenty of time but knew the clock was ticking. I met the Captain in Operations but we had to get a ride from Ops to the hanger where the aircraft was parked. Maintenance was busy and our ride was 30 minutes late. We would have made our scheduled departure time and our returning DH flight had we made it to the hanger on time but with the delay we were a bit rushed trying to get our preflight done to make our scheduled DH.During preflight; Maintenance asked the Captain if he wanted to transfer fuel from the center to the main tanks. He said no because there were 4;900 pounds of fuel in the center tank (main tanks had 6;000 pounds) and that he was sure he was allowed up to 5;000 pounds in the center tank with the main tanks less than full. I did not process the conversation I had overheard until later at cruise; as I was wrapped up my preflight duties and didn't want to hold up our departure so we could make our DH. We took off with that fuel configuration; and when things settled down at cruise; we talked about looking up the fuel issue to make sure it was correct and then realized we took off with the fuel out of limits. The flight arrived without further incident.


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


Synopsis: Large transport flight crew departed and flew with a non-SOP fuel loading.
Date: 201808
Local time of day: 0601-1200
Location: DEN.Airport, CO
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Taxi
ATC / advisory: Ramp DEN
Second aircraft: Commercial Fixed Wing
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; Distraction
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were operating as a ferry flight with only FAs (flight attendants) onboard. We pushed from [the] gate cleared by Ramp to taxi BS to 4E for Runway 17R. We taxied on BS toward 4E and Ramp cleared us to switch to Ground. We have not received our final weights yet; so FO (First Officer) was busy calling station Operations on R VHF to request final weight while we both monitored Ground on L VHF. Thunderstorms were just east of the field and Ground is telling another aircraft their departure route is closed. I was looking out to the east and south to evaluate the weather for our departure. Then I heard FO yell 'STOP STOP STOP!' just as I started to follow the slight left jog in BS at 4E. I stopped the aircraft; set the parking brake and saw [another aircraft] being pushed back and its tail was well within our left wingspan's path. They continued to push back and had we not stopped; we would definitely have hit the [other aircraft]! Their wing walkers never clear the path! Even with us stopped right beside them; they still continue to clear the aircraft to pushback farther! FO tried to call Ramp again to inquire about the pushback into our path. Ramp's response was that she was not talking to the [other] crew; they were talking to their push crew. She suggested we can go to AN to Ground there; but we had insufficient clearance for our left wing to do the right turn without hitting the [other aircraft]! Both the FO and myself also observed the ramper gave the cleared signal for the [other aircraft] even when their tug was still attached to the aircraft! Their pushback crew and wingwalkers clearly were not doing their job properly! We told Ramp that we could not taxi until the [other aircraft] is out of the way; so she cleared them to turn west and circle behind us. Once the [other aircraft] was out of the way; we continued to 4E and switched to Ground. Distractions for us were the late final weights; weather for departure; and [the] FO did a great job by noticing the incursion and told me to stop the aircraft; thus avoiding a ground collision!




Synopsis: Air carrier Captain of a passenger aircraft reported a near collision with another aircraft while taxiing out for takeoff.
Date: 201912
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Dawn
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Airspace: Class B ZZZ
ATC / advisory: Ramp ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Private; Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Distraction; Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I tore the Crew listing off the blank ATIS sheets to put on the Captain's side by the HGS dim control knob. The HGS was MEL'ed and had a stricter under the dim control knob. I didn't want to cover up the sticker; so I elected to try and put the Crew listing on the ledge above the lower DU. When I tried to balance it there; it slipped behind the lower DU. I should have stopped what I was doing right then; told the Captain; and called Maintenance. Instead; I elected to do my walkaround and inform everyone after; in case I found something else on the walkaround. I completed my walkaround uneventfully and got sidetracked with conversation with the Gate Attendant; Flight Attendants; and Captain as I completed my preflight duties and completely forgot about the Crew listing slipping behind the lower DU. After completing the flights for the day and getting to the hotel; I remembered I didn't report the incident. I called my Chief Pilot and the on call Chief Pilot to report it. I talked to the Maintenance Rep and told him the story too. The Maintenance Rep told me the aircraft was due to land in ZZZ and they would check it out; but felt it was not a going to be a problem.




Synopsis: First Officer reported that distraction caused him to forget to inform the Captain and Maintenance about an issue.
Date: 201704
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight
Result: General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We experienced a very hard landing. The aircraft landed hard once; took a leap back in the air and came back down hard again. Jolted passengers in their seats; startling everyone. After everyone was off the aircraft I asked the captain what had happened. Most passengers made some rude comments leaving; I apologized and wished them a nice day. Both pilots did not get out of cockpit until everyone was off. Was told by the captain the FO was flying and had very little experience. The FO left immediately after all passengers got off. Captain stayed and spoke to me. Captain asked how hard it had felt for us in the cabin. I told him it was pretty bad. I asked him what he was going to do and he said he was thinking about it. He was done for the day so he was not going to continue; but myself and the other FA would be on same aircraft for next flight out. I then asked him to please do something out of the safety of the next crew and the passengers. I told him I didn't feel comfortable without someone looking at the aircraft before flying out again. He said he was still thinking about it. Once the new captain came in the aircraft I told him what was going on; while the other captain was still in the cockpit debating on what to do. The new captain then went to speak to him and decided then to report the incident. We were then transferred to a new aircraft creating a delayed flight but everyone was safe.




Synopsis: CRJ900 Flight Attendant reported a very hard landing that the Captain seemed reluctant to enter into the logbook. The oncoming Captain was informed and the aircraft was taken out of service for inspection.