elihoole/asrs-aviation-reports huggingface dataset:
Date: 201203
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Air Carrier X was cleared for the ILS [Runway] XX approach; but was not put on the Tower frequency. I did not realize this until Air Carrier X said he was responding to an RA. I told him it was parallel traffic off his right and [asked if] he wanted to continue the approach. He said yes; so I told him to contact Tower. Two miles later he told me he was going around. I told him to climb to 5;000 FT on the localizer and; again; contact the Tower.




Synopsis: TRACON Controller failed to change an aircraft conducting a parallel approach procedure to the Tower as procedurally required; resulting in a TCAS RA and go around.
Date: 202011
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise; Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
Result: General None Reported / Taken
Contributing factors: Company Policy; Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Passenger X boarded the aircraft and proceeded to self-upgrade himself to a better seat.  When he was asked about this by another FA; he held his ground.  Apparently; out in the gate area; he was quite belligerent.  So; a member of the ground staff had to come on board and move him back to his assigned seat.  He said that he was fine.  After takeoff and constantly throughout the flight; I had to ask him to put his mask on.  It happened several times.  He was not happy that I kept asking him.  I guess he felt that he was exempt from the wearing of masks.




Synopsis: Flight Attendant reported a passenger was not compliant with face mask policy and also moved to a better seat without asking FAs.
Date: 201809
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp ZZZ
Aircraft component: Nose Gear
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict Ground Conflict; Critical; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Taxi
Result: General Maintenance Action
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: During pushback from gate in ZZZ; the tug suddenly stopped; causing [a] small bump to the airplane. Fortunately; no one was injured; however; the reason for the stop was due to a ZZZ Airport Operations vehicle crossing dangerously close behind us during the pushback. Because of the quick stop; the nose gear pin sheared and Maintenance was called to do an inspection of the nose gear. No damage was found by Maintenance.




Synopsis: A320 Captain reported the tow bar pin sheared during pushback due to the tug suddenly stopping.
Date: 201506
Local time of day: 0001-0600
Location: EWR.Airport, NJ
Flight conditions: IMC
Weather elements / visibility: Rain
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Flight plan: IFR
Flight phase: Other Parked pre-departure
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Weight And Balance
Detector: Person Flight Crew
Result: Flight Crew Took Evasive Action
Contributing factors: Equipment / Tooling; Human Factors
Primary problem: Ambiguous

Narrative: I received final weights before pushback. I appropriately carried over the final weight information and loaded the departure runway; 4L; and our gate weight and runway conditions. Moments later we received the takeoff data and I accepted the V Speeds prompt; then showed the Captain the weight message and Takeoff Data printouts side by side as I always do so both pilots verify the information. We agreed to commence the pushback checklist; but then he paused and suggested we review the Takeoff Data one more time; citing it didn't look quite right. After we both scrutinized the Takeoff Data Message for some time (at the gate; no pushback occurred); the Captain thought we may be looking at takeoff data FOR THE ARRIVAL CITY not the departure city. Runways at both airports have same numerical assignment (RWY 4L). We checked every single page of the ACARS initialization page and found the flight number; departure city; arrival city; all correct. Release correct. Before initiating any 'reset' or 'start all over' process; I suggested we call our dispatcher and describe the anomaly. Captain telephoned our dispatcher who had no answer as to the cause; but pushed the Takeoff Data 4L to the aircraft printer and we manually loaded the performance from the dispatcher's Takeoff Data printout into the Perf Page in ACARS. I attached images of the weight message; the erroneous Takeoff Data Message showing 4L at the arrival city; and the dispatcher's 4L Takeoff Data message for the actual departure airport he pushed to our printer himself. While standardization; proper CRM; and crew attention to detail resulted in a safe; legal departure; it is concerning that [the computer software] can give us Takeoff Data to the exact same numbered runway; but for the destination airport not the departure airport. In a rushed; fatigued; busy airport environment; or had there been an inexperienced crew in our shoes; a departure could have occurred without correct [though more conservative] takeoff data in the FMC.




Synopsis: Air Carrier First Officer; planning on departing Runway 4L reports receiving V speeds for Runway 4L at the arrival airport. The Captain caught the error during the takeoff briefing and the crew contacted their Dispatcher; who could not explain the error but sent new data.
Date: 201510
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Nose Gear
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Distraction; Situational Awareness; Confusion
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Maintenance
When detected: Other push tractor pulled gear
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was pushing aircraft to park at hangar. Once chocked was going to pull the push tractor back and in to set it up for a crewmate to pull the pin out. As I thought I had my foot on the brake had it on the accelerator; the tractor lunged backwards and pulled the front nose strut out and the aircraft collapsed. Nobody was injured and all were safe.




Synopsis: A Maintenance Technician reported a nose landing gear collapse when the tug was unintentionally accelerated in reverse.
Date: 202010
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B787 Dreamliner Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Other / Unknown; Distraction
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew; Person Dispatch
When detected: Other Pushback
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Received planned DG [Dangerous Goods] report during pre-flight.  Discussed needing to wait for final DG report during brief but got distracted and temporarily forgot we did not have final DG.  Pushed as DG final was being sent.




Synopsis: B787 First Officer reported gate pushback initiated without final DG report.
Date: 202003
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: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Company Policy
Primary problem: Company Policy

Narrative: There was not a bottle of [disinfectant] to wipe down the galleys with. Nor were there any sanitation wipes or masks in the Flight Attendant kit.  Both forward and aft; so we broke into the kit; after we notified the CSA (Customer Service Agent); and waited for some one to bring these 3 items to us before departure. We were told that they were out of it. If we are going to get a 'must read' bulletin...about bottle that would be on board; and location on both equipment; then why isn't there? This is the second time had to request it out of ZZZ.On another note; when we arrived in ZZZ1; I asked for the bottle of [disinfectant] for the outbound crew; face masks and clean wipes; didn't get those either. The flight went back to ZZZ with no masks. I sure hope that they didn't have a medical; or weren't exposed to an infected guest.  We need masks; sanitation wipes and [disinfectant] spray bottle on all aircraft.Please make sure that all of the sanitation items are on all aircraft; and the inbound FAs are making sure that if there aren't any left on inbound; that they requested them for the outbound to be replenished.




Synopsis: Flight Attendant reported that the kit on the aircraft did not have required sanitation supplies or masks. In addition; these supplies are not being replenished in between flights.
Date: 201306
Local time of day: 0601-1200
Location: PSP.TRACON, CA
Flight conditions: VMC
Weather elements / visibility: 20
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class D PSP
ATC / advisory: TRACON PSP
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Private
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was on personal flight testing new Garmin GDL 39. I had disconnected my XM weather antenna to check function of GDL 39. The GDL 39 was not functioning properly and therefore did not warn me of my proximity to the TFR. Because this was an area flight in an area I fly often; I did not check NOTAMs that morning; big mistake on my part. To prevent such an incident; always check NOTAMs; regardless of the purpose or proximity of any flight.  Also leave all available equipment functioning at all times if it can give information regarding the flight. If I had left the XM antenna attached; it would have warned me of the TFR in my area of flight.




Synopsis: Lancair pilot reports an inadvertent entry into a TFR in his local area due to not checking NOTAMs and an inoperative GPS map display.
Date: 201807
Local time of day: 0601-1200
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: Dangerous goods not properly strapped and tied down on pallet. Direction arrows on DGR (Dangerous Goods Regulations) goods not taken seriously and goods tilted to the side.




Synopsis: Company Safety Manager reported Dangerous Goods had not been loaded in accordance with Dangerous Goods Regulations.
Date: 201209
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Beech 1900
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Gear Extend/Retract Mechanism
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Landed in Emergency Condition; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Approach was uneventful until it was time for the gear to be extended at the glide slope intercept point. The First Officer and I noticed that the top; nose wheel gear indicator; was extinguished. We first tested the indicator as good; then; cycled the gear. We then requested to discontinue the approach to work out the issue. After running the appropriate check-list in the QRH; I declared an emergency and notified the passengers of the situation. I decided that my landing techniques could land the aircraft much softer with less stress to the nose gear than the First Officer could; so; prior to commencing the approach; I had the First Officer practice to pump the gear handle and to assure that he could reach the handle positions just prior to touch down. We saw that he could easily accomplish this task. We then requested a visual approach. The plane touched down gently and we slowly taxied off to the high speed. I stopped the aircraft and requested Maintenance to secure the landing gear. I taxied the aircraft to Customs and deplaned.




Synopsis: BE1900 Captain reports failure of the nose gear to extend during approach. An emergency is declared and manual gear extension procedures in the QRH are complied with. An uneventful landing ensues.
Date: 201810
Weather elements / visibility: Turbulence; Thunderstorm
Light: Night
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Aircraft component: ACARS
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Company Policy; Weather
Primary problem: Ambiguous

Narrative: Was unable to communicate with Company/Dispatch to receive ETOPS weather update; tried all HF frequencies for ZZZ Radio. Unable to make contact. ACARS doesn't work internationally and aircraft did not have a SATCOM installed. We considered an air turn back to [departure airport]; but due to the thunderstorms on the return route; we decided continuing the most prudent action as we knew [alternate airport] was VFR. At no point was safety compromised.ACARS needs to be worldwide operable; [and also] add a SATCOM to the aircraft.




Synopsis: Aircraft are not equipped with worldwide ACARS nor SAT Phones and were unable to reach company/dispatch.
Date: 201901
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Balloon
Operating under: Part 91
Flight plan: VFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class D ZZZ
Aircraft component: Air/Ground Communication
Component problem: Malfunctioning
Reporter organization: Contracted Service
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: I was carrying 6 passengers and one Student Pilot. After using helium balloons to determine wind direction; we planned to travel about 7 miles and land at [a predetermined] field. Shortly after takeoff; the wind speed picked up from 5 mph to 18-24mph between ground level and 3000 feet. The direction had changed as well. With these wind speeds; I was unable to safely land the balloon in our routine flight corridor due to lining up with trees; boulders; streets or power lines on my first couple of landing attempts. At this time; I elected to land in the large fields [near an] airport. These fields were 13-16 miles further east than the originally planned landing sites. After the decision to climb over 3000 feet MSL; I tried to establish radio communication with the airport Tower. My radio did not have a charge. I instructed the Student Pilot to search his cell phone for a phone number to the airport. He tried several phone numbers and could not get a hold of anyone. He was unable to retrieve the 1-800 number for Approach on his cell phone search. My concern was on flying the balloon and navigating my passengers to a safe field to land. I was constantly scanning for a field large enough to deflate the balloon in 18-22mph wind while avoiding power lines; boulders; trees and other objects. We safely landed in a field. I had entered the Class D airspace without radio communication and committed a pilot deviation. I had tried my best to make contact with the Tower but after a few failed attempts on my end my attention was focused on the flying and navigation of the hot air balloon to land my passengers and myself safely. In the future; I will double check that the aircraft radio is in working order before flight




Synopsis: Hot air balloon pilot reported a change in the wind direction and velocity required a new landing spot. After being unable to contact ATC for clearance; the only option was to enter and land with Class D airspace.
Date: 201702
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Failed
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 Landed As Precaution; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [At] FL350 master caution light started to flicker; along with left hydraulic low pressure light on overhead panel illuminated. hydraulic system A quantity at 10%. [Advised ATC of the situation.] Completed QRH checklist; notified dispatch and station. Landing uneventful. Entered in the logbook.


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


Synopsis: B737-800 flight crew reported diverting to an alternate after the left hydraulic system A quantity went to 10%.
Date: 201505
Location: OAK.Airport, CA
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C OAK
ATC / advisory: TRACON NCT
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: This event is the second time in the last month where NorCal Final Approach into OAK ILS30 places aircraft too high for ILS intercept (arriving from north; right downwind).  The glideslope commands a descent prior to localizer intercept.  Once the aircraft is established; it becomes a struggle to get down and re-stabilize.  As an example; both times; the workload was so intense that the FAF was not verified and crosschecked.  Time and frequency congestion have limited the ability to request lower (prior to intercept).  Although both approaches met the stable criteria; I believe that tight and high vectors contribute to destabilizing an approach.




Synopsis: A pilot reports of being high and above the glideslope while flying into OAK airport on the ILS to runway 30. He is kept high by NorCal approach.