elihoole/asrs-aviation-reports huggingface dataset:
Date: 201808
Local time of day: 1201-1800
Location: ZJX.ARTCC, FL
Flight conditions: Marginal
Weather elements / visibility: Thunderstorm
Aircraft: Small Transport
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZJX
ATC / advisory: Center ZJX
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Workload
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Staffing; Weather; Human Factors; Airspace Structure
Primary problem: Airspace Structure

Narrative: I was working the radar and the sector got busier and busier. I asked for an Assist position. Someone was paged back from a break. Aircraft X called for clearance. I had numerous weather deviations with many MOA's active. Jacksonville arrivals were going in and out of ZJX airspace through weather and TMU (Traffic Management Unit) hadn't shut that off. Even a pilot asked why he was turned into weather from another sector. There wasn't enough room for all of the planes to get through all of the weather. I gave Aircraft X a clearance and tried climbing above Approach airspace but the airspace is too close and nearly every plane needs a point out that climbs from SSI northbound. The Assist sat down and I saw Aircraft X was in Approach airspace by about a mile. I called Approach and they approved a point out.If the Savannah or JAX Approach extended their boundary it could encompass SSI; BQK; JES and 09J airports. This geographical area is more suited for what approach does. Give them 10;000 ft or 15;000 ft and down. The staffing in the North area is always low. The other areas always seem to have more staffing than the North. If the areas were balanced there would be more people with Assists probably already in the area. This may not have happened if an Assist Position was already close by. TMU never shut off the inbounds and outbounds at Jacksonville. There seems to be more of a priority to call the precipitation rather than to route planes away from the weather. I had to stop inbounds and outbounds to JAX. There was little to no weather on the west side of JAX and little to no traffic. Things never should have gotten to that point. To prevent a reoccurrence [there needs] to be a rethinking of what TMU does. The volume of traffic in that degree of weather could have been avoided. TMU did not cause Aircraft X to go into Approach airspace but the complexity of what was going on contributed to me not catching it in time.




Synopsis: ZJX Center Controller reported not having enough time to point an aircraft out to another sector due to workload and weather deviations in their sector.
Date: 201301
Local time of day: 0601-1200
Light: Daylight
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: Oxygen System/Crew
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Workload; Situational Awareness
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While at cruise at FL370; during 2nd half of second bathroom break; PNF became aware of a lack of O2 pressure from his mask. Gauge on overhead indicated near zero. Conferred with Dispatch (weather and fuel burn); Maintenance and FOM and descended to FL250. We positioned a therapeutic O2 tank on flight deck with 2 masks unwrapped and ready to use and continued to our destination without further problems. Did not hear the result from Maintenance but assume an oxygen leak.


Second narrative: On second Biffy break; I noticed a lack of 02 in my mask and on the overhead gauge. We set up a therapeutic bottle with two masks at the ready; checked destination weather; reviewed FOM guidance; verified time and burn at FL250; requested descent clearance and advised Dispatch\Maintenance.


Synopsis: During cruise flight the B737-800 Captain noticed no oxygen in his mask while the First Officer was on a physiological break; and; assuming a leak; had a cabin supplemental bottle and two masks brought to the flight station and descended to FL250.
Date: 201305
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Weather elements / visibility: Thunderstorm
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft; Company Policy
Primary problem: Aircraft

Narrative: Climbing through about 17;000 FT we received a pack temp ADV. The Captain read the QRH and complied. I flew and communicated with ATC. The Captain was able to momentarily cause the ADV to go out; but the pack continued to overtemp irregardless of pack valve configuration. We elected to return to the departure airport since the QRH states that if the ADV is uncontrollable we should turn the pack off to let it cool down. We landed without incident.The main issue was that the #1 Pack was already deferred.




Synopsis: An A300 dispatched with the #1 Pack MEL'ed; received a #2 PACK TEMP ADV while climbing and elected to return to the departure airport because they were unable to control the #2 pack.
Date: 201501
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cheetah; Tiger; Traveler AA5 Series
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Air/Ground Communication
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial
Human factors: Workload; Situational Awareness; Communication Breakdown; Confusion
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Landing Without Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Landed As Precaution
Contributing factors: Human Factors; Procedure; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: Student again after 32 yrs inactive; arriving at my destination from the North under the Class B airspace; obtained ATIS info. Subsequent attempts to raise Tower were unsuccessful. Seeing no signals or lights from the Tower after repeated attempts to call; pilot entered pattern per ATIS for Rwy XXL and proceeded to land; observing a Cherokee and one other plane holding short; and being prepared for a go around; and watching Tower. Ground informed pilot that he had landed without permission and that Tower frequency was not XXX.4 but XXX.1. The reason pilot could not raise Tower was due to having the wrong frequency and did not use resources at his disposal to recheck the frequency.Student learned that extra care under stress (transiting under busy Class B Airspace for the first time ever); and that triple checking preflight info; including reviewing resources to solve the problem once encountered could have been used at the time before proceeding.




Synopsis: An AA5B pilot with little recent flight experience landed at a Class D airport below Class B without landing clearance because he selected the incorrect Tower frequency.
Date: 201901
Local time of day: 0601-1200
Location: LGA.Airport, NY
Flight conditions: IMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation - Altitude Undershoot; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While on the KORRY 4 arrival into LGA; Washington Center instructed us to cross RIDGY at FL270. The pilot flying set FL270 on the altitude select and managed the descent. The FMS was programmed to cross RIDGY at or above FL270. We forgot to reprogram the FMS to cross RIDGY at FL270. After a couple of minutes we realized our error and we knew we will not be able to make the altitude restriction. We informed Washington Center that we will not be able to make the altitude restriction. Washington Center instructed us to descend to FL240.Make sure to verify and check that the proper altitude restriction is programmed in the FMS.




Synopsis: A320 Captain reported failing to make a crossing restriction at RIDGY that was modified by ATC on the KORRY 4 arrival into LGA.
Date: 201404
Local time of day: 1801-2400
Location: ZLA.ARTCC, CA
Aircraft: Small Transport
Flight plan: IFR
Flight phase: Cruise
Airspace: Class E ZLA
ATC / advisory: Center ZLA
Second aircraft: Medium Transport; High Wing; 2 Turboprop Eng
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion
Second reporter function: Handoff / Assist; Enroute
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Provided Assistance
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: Aircraft X was landing TRM but currently stuck above Aircraft Y overflight to NZY. When I took the sector Aircraft Y additionally was at 11;000; an atypical altitude for his flight direction. Aircraft Y was outrunning Aircraft X and soon we would be able to descend Aircraft X for landing at TRM and then get Aircraft Y down to his requested altitude of 10;000. Aircraft X planned to cancel if he could descend lower on the visual approach so I asked my D-side to point him out to Springs Sector; the SCT sector that owned airspace above TRM airport. He completed this coordination but advised that Springs Sector wanted to take radar. Aircraft X was cleared for the visual approach and then shipped to Springs Sector. Apparently the SCT Controller had traffic and although he accepted the coordination (my D-side restated the clearance to him to be sure) he didn't realize what [conflict] he had created. He never gave us an alternate control instruction but later complained that our coordination was improper. In fact he disregarded or misunderstood the entire exchange. His unusual response to take radar made my D-side wary enough to restate the clearance and the SCT Controller still said nothing about it.I was not party to the D-side/SCT coordination and only got to hear it after the fact via FALCON but; as my D-side suspected; it appears the SCT Controller did not understand our intentions. If I had heard his response I may have instead returned to the LOA procedures so as not to confuse the apparently busy SCT Controller.


Second narrative: While coordinating an unusual request from my veteran R-side; Aircraft Y was descended into Palm Springs approach shelf without a point out. After getting off the line and completing a scan; I noticed that Aircraft Y had been descended into the shelf and subsequently pointed him out. My R-side had asked me to point out another aircraft which the Approach Control did not approve. I'm not sure if my R-side thought I pointed out the Aircraft Y or not; but no coordination was done regarding this aircraft.Try to keep a better scan while on the line with other sectors and make sure the R-side knows what I've done and have not done.


Synopsis: ZLA Controllers describe a situation where communication between hand off and another facility Controller could have been better.
Date: 202010
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Bombardier Learjet Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuel Distribution System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb; I tried to start moving fuel forward with the gravity flow valve open and noticed that it didn't work. Then I tried the normal transfer valve and nothing happened; my last resort was the rapid transfer system and it didn't work either. I then tried to open the crossflow valve and nothing happened. I checked the circuit breakers and noticed the crossflow valve breaker was out. I asked my FO (First Officer) to start looking for an airport to land since we were not going to use our fuel from the fuselage tank. The airplane was not showing any indication of any of the fuel valves working; I notified my company of the incident while I was looking through the airplane manual to try to reset the circuit breaker. After I tried it once and noticed it didn't solve the issue; it kept popping out; I commanded my FO to notify ATC and initiated a descent and turn towards our closest suitable airport. Our fuel from the wings kept getting low and after great coordination with controllers we were able to get safely to the ground. Possible power surge changes in such an old and poor maintained airplane lead to crossflow valve to fail also causing other valves and indications to malfunction.




Synopsis: Air Taxi Flight Crew flying Learjet report fuel transfer malfunction during initial climb.
Date: 201307
Local time of day: 1201-1800
Location: ZZZZ.ARTCC, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: Center ZZZZ
Aircraft component: Cockpit Window
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Human factors: Workload; Distraction
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon climb out; right front First Officer window malfunction prior to oceanic airways entry at FL300. Sudden window cracking at FL300 along with a loud bang. QRH procedures were applied; emergency declared and worked with ATC to return to the departure airport. Flight attendants; OCC and Ops were advised as well as passengers. Made an overweight landing; with emergency vehicles standing by. Landing was normal; taxi in to gate normal followed by report from fire rescue that brake temps were not excessively high. Local Maintenance arrived at the gate and were briefed; logbook entries made and OCC was contacted. The flight was canceled and we deadheaded back to PHL the next day.


Second narrative: We declared an emergency and received a clearance back to our departure airport with a descent to 10;000 FT. We applied the appropriate QRH procedures (including that for an overweight landing). We notified OCC; briefed the flight attendants; and advised the passengers. We landed uneventfully on Runway 24 with emergency vehicles standing by. On arrival; I had a conference call with OCC; MOC; and the Tech Rep from Airport Aerospace. I made logbook entries for the damaged window and an overweight landing. The flight was canceled and the passengers deplaned.


Synopsis: A B757-200 right cockpit window cracked with a loud bang so an emergency was declared and the flight returned to the departure.
Date: 202006
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Distraction; Fatigue
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Equipment / Tooling; Procedure
Primary problem: Procedure

Narrative: While performing an inspection of the #2 engine VG (variable geometry) actuating system on Aircraft X; I found a screwdriver resting under the W1 harness. Upon discovery of this I removed the tool; inspected the area for damage; and brought the tool to my Supervisor. No damage was done to the harness; tubes; brackets; or components however it had the potential to become a serious issue. I suggest the following to help prevent any events in the future: 1. Work areas such as engines; wheel wells; hydraulics bays should not be used to set tools in as a tray. 2. Always account for the tooling used on the job after work is complete. 3. Do a final inspection of the area that was worked in for FOD (foreign object debris/damage) or tools before you close the panel or engine.




Synopsis: Technician reported performing a routine; scheduled inspection on the number two engine VG actuating system and finding a screwdriver resting on the W1 wire loom of an EMB-175 aircraft.
Date: 201901
Local time of day: 0601-1200
Weather elements / visibility: 10
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Landing
ATC / advisory: UNICOM ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Human-Machine Interface
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Other on landing
Result: General Maintenance Action
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: Upon landing; aircraft veered off runway (010) to the left side; struck a runway landing light and then became stuck in a muddy area off of runway. Pilot is unsure what caused the sudden veer; possibly pilot error in landing speed and judgement. Damage to aircraft resulted in two wheel pants/skirts needing repair.




Synopsis: C172 pilot reported a runway excursion due to loss of directional control during landing roll.
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: Other All Phases
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Distraction; Situational Awareness; Troubleshooting; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Company Policy
Primary problem: Environment - Non Weather Related

Narrative: I was the least involved crew member. Passenger X was assigned to seat XX2 but upgraded herself to YY6; an exit row seat next to her friend. The A [FA] gave her a mask when she boarded because she only had a scarf. Passenger X had food in front of her for much of the flight so that she wouldn't have to wear a mask. I picked up her food trash about 1 1/2 hours into flight and advised Passenger X that she needed to wear a mask. Fellow FAs had told her that she needed to wear a mask previously while not eating. She stated; 'I won't' very clearly.Suggestion - Have a National Policy on mask wearing and ban passengers that fail to comply. This passenger told my coworkers that she didn't intend to fly our airline again. A coordinated policy might have more teeth; and since these passengers are failing to comply with crew member instructions; consider a permanent ban.




Synopsis: Flight Attendant reported a passenger was not compliant with face mask policy.