elihoole/asrs-aviation-reports huggingface dataset:
Date: 201901
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: It was brought to my attention by the oncoming CA (Captain) that MX (Maintenance) had discovered the crew O2 (Oxygen) level was low. MX had also found; sometime after our arrival; that the O2 valve was in the closed position. To the best of my knowledge; the proper O2 checks were done before we left [our departure field]; including the 10 second bleed test that was done by my FO (First Officer); with no abnormalities noted. We did not note any discrepancies upon arrival; although neither the FO nor myself recall checking the O2 level after landing; as this is not included in any post flight duties. I would suggest closer attention be paid to the O2 levels in flight. This does take a conscious decision as this page is not normally displayed in flight. Do not make assumptions that proper MX procedures are followed; as the logbook was stamped that it was approved for return to service. Always back yourself up.

Callback: The reporter explained that there were no problems with the oxygen system during his flight. After the flight (about 2.5 hours after he left the airport) he was contacted by the oncoming flight crew who said the Crew O2 level was low and the O2 valve was in the closed position. He had no idea how that could have happened. The on-coming crew suggested he file a report even though he did not detect any anomalies during his flight.



Synopsis: B767 Captain reported that the crew O2 level was found low during pre-flight by the next crew on the aircraft.
Date: 201604
Local time of day: 1801-2400
Location: OGD.Airport, UT
Flight conditions: VMC
Light: Night
Aircraft: Small Transport
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Climb
Airspace: Class B SLC
ATC / advisory: Tower HIF
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Distraction; Communication Breakdown; Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: On climb out I made a right turn to fly up the canyon southeast of Ogden towards Heber City. I normally contact Hill tower for a transition through their delta surface area for this flight. I attempted to contact Hill tower; but they were not open. As I was distracted figuring this out; I received a terrain alert from the aircraft as I was approaching rising terrain. I pulled up and made a sharp right turn to resolve this; in so doing I crossed into SLC's Bravo airspace briefly without clearance. The main cause was my erroneous assumption that Hill tower is a 24/7 operation as many military towers I have previously dealt with in the area. A contributing factor is the tight arrangement of the airspace in and around Ogden/Hill area that does not allow VFR to pass between the mountains and the airspace without clearance.




Synopsis: A general aviation pilot reported an airspace violation and a terrain alert while climbing out from Ogden Utah.
Date: 201909
Local time of day: 1201-1800
Location: TPA.Airport, FL
Flight conditions: VMC
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZJX
ATC / advisory: Center ZJX
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Security; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Result: General Police / Security Involved
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: 3 coach Flight Attendants noted a 10-year old girl in seat 12B that had two adult women seated around her; in seats 12A and 12C. The adult women were rude to the Flight Attendants. The Flight Attendants (with many years of experience) felt they saw several indications of human trafficking and notified the flight deck of their observations. The flight deck contacted Dispatch and the Flight Operations Duty Officer and declared a Level 1 security situation to Dispatch. Dispatch advised the arrival station (Tampa) of our onboard situation and that a Ground Security Coordinator would meet the flight on arrival. The rest of the flight and arrival proceeded without incident; and Tampa airport police and the Ground Security Coordinator met the flight at the gate. The flight crew was not advised of any further issues and finished post flight duties normally.




Synopsis: B737 Captain reported that Flight Attendants believed they saw a child who was the possible victim of human trafficking.
Date: 202012
Local time of day: 1201-1800
Location: DUY.Airport, AK
Weather elements / visibility: Snow; 10
Light: Night
Aircraft: Small Aircraft
Operator: Air Taxi
Operating under: Part 135
Flight plan: VFR
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
Reporter organization: Air Taxi
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting; Situational Awareness; Confusion; Distraction
Anomaly: Ground Event / Encounter Object
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors; Airport
Primary problem: Airport

Narrative: When I arrived at DUY there was another aircraft parked in the ramp area and it began to taxi out before I vacated the runway. The previous aircraft had offloaded cargo in the center of the ramp but I failed to see it due to the ramp being unlighted and the difficulty of seeing over the engine cowling. The aircraft's taxi light is also located in one wing and doesn't illuminate objects on the other side of the aircraft very well.While taxiing onto the ramp; the propeller contacted a cardboard box from the previous aircraft's cargo. There was no damage to anything outside of the cardboard box and there were no injuries involved.The ramp area at Kongiganak is very constricted and requires a lot of effort to operate safely in the best of circumstances. I feel that this episode might not have happened had the previous aircraft unloaded its cargo in a less hazardous location. At DUY the runway is lighted but the ramp is unlighted. If the ramp area had better lighting; then this unfortunate episode might have been avoided.




Synopsis: Pilot reported hitting cargo during taxi on an unlighted ramp at DUY airport.
Date: 202008
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operating under: Part 91
Flight plan: IFR
Flight phase: Taxi
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General Flight Cancelled / Delayed
Contributing factors: Aircraft; Human Factors; Staffing
Primary problem: Staffing

Narrative: Working short staffed again. Forced to work local center; local east; and city combined. Worked a two hour busy session that is usually split between 3 controllers. Plus the Supervisor was working ground so I did not have line up and wait. There was frequency congestion throughout and pilots repeatedly had to repeat transmissions. Aircraft X requested Runway XXR due to weight and the hot day. Because that runway was busy with arrivals; he had about a 15 minute delay. No request was made to switch arrivals because the 'TMC' was too busy working ground. I was also limited in my coordination's because of the busy traffic. The airport has construction all over which adds to the complexity with back taxiing aircraft and extra coordination on ground. I was extremely fatigued mentally towards the end of my position but there is nothing anyone could do because of our ridiculous staffing.I felt unsafe working those positions combined with that traffic load. Especially not having a supervisor watching what I was doing. This entire week has beat me down and I am beyond frustrated. Now I am having trouble sleeping because of work. But I know I have to go in because I will only make it worse for other controllers if I don't. Management refuses to slow the arrival rate (despite controllers requesting it) even though it is absolutely needed during that time and many others. A couple departures were delayed because I couldn't line up and wait and the TRACON simply continued pushing arrivals like it was any other day. We are expected to work full traffic loads with combined positions and no oversight. This is an emergency situation; I understand that. But why are we not being protected? Why are there people eligible to work OT that aren't assigned it days in advanced? Everything this summer has been forced down our throats and controllers are fed up. The facility safety culture going forward will be difficult because management has shown us what they think of collaboration. I don't know if anyone even reads these reports. I don't get any feedback. But I am keeping a copy in case something catastrophic happens. I want it documented that this was foreseen.




Synopsis: Tower Controller reported a busy session working three combined positions and having to delay an aircraft for 15 minutes due to traffic.
Date: 201302
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument
Second reporter function: Passenger
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Arrived for orientation ride with son and grandson. Preflight was normal; placed a warm air heater in the engine induct for preheat. Went over checklist items with son as an introduction. Loaded up the aircraft with grandson in right rear seat; son in left front seat and myself in right front seat. Engine start; taxi; and takeoff was normal. Flew one touch and go to the runway without incident. I allowed my son to fly the pattern; which was wider and longer than I would normally do but was not concerned because we were the only aircraft in the pattern. During the second pattern; on turn from downwind to base; the engine quit. We were already configured with gear down and half flaps. We were at approximately 1;300 feet MSL and 3 miles from the end of the runway. I took control of the aircraft. I could see that I was not going to make the runway and began setting up for a landing on a parallel road. I selected the opposite fuel tank but did not turn on the fuel boost pump. I landed on the road but during roll out the right wing struck a wooden road sign. This caused the aircraft to veer hard right and depart the road. The aircraft came to rest in a plowed field. We egressed the aircraft normally.


Second narrative: During our second pattern on the turn from downwind to base the engine quit. My dad immediately took control of the airplane and we landed on a parallel road to the runway.


Synopsis: Small aircraft had an engine failure in the airport traffic pattern. Pilot lands off airport and aircraft veers into a plowed field.
Date: 201902
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: Situational Awareness
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
Primary problem: Environment - Non Weather Related

Narrative: Upon arrival; there was no [Gate] Agent. While waiting; [Catering] in the back of aircraft started to open the galley door while the door was armed; flag across window and closed. I yelled 'no' and forced the handle back down. After a few minutes; [Flight Attendant] A said 'disarm and cross check for arrival.' At this time; I disarmed my door; removed the strap from the window and cracked the door and made PA. [Catering] explained and showed me due to the sunlight/glare you could not see the flag through the window. Slide did not deploy.




Synopsis: Air carrier Flight Attendant reported ground service personnel attempted to open the galley door when it was still armed shortly after arrival; and explained they could not see the flag through the window because of sun glare.
Date: 202006
Local time of day: 0001-0600
Location: GTF.Tower, MT
Flight conditions: VMC
Aircraft: Cessna Citation Mustang (C510)
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Ambulance
Flight phase: Final Approach
Airspace: Class D GTF
ATC / advisory: Tower GTF
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure; Workload
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: A VFR aircraft ground looped on the runway. While Aircraft X was on final. The local controller who was also the Controller in Charge started the procedures for getting things taken care of. This caused the airport to close the runway and for me to cancel Aircraft X's approach. While he was on final I asked him if he could take a different runway which he replied that he could. I cleared him for the Visual Approach and was going to switch him to the tower when I noticed that the Local Controller was very busy taking care of everything that was going on. I coordinated my control of Aircraft X and cleared him to land on my frequency. A Ground controller would have been nice or maybe even a stand alone Controller in Charge.




Synopsis: TRACON Controller reported they had to issue a go around and diversion to another runway due to a disabled aircraft on their runway.
Date: 201411
Local time of day: 0601-1200
Location: PHX.Airport, AZ
Flight conditions: VMC
Weather elements / visibility: 40
Light: Daylight
Aircraft: Citation V/Ultra/Encore (C560)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Airspace: Class B PHX
ATC / advisory: TRACON P50; Tower PHX
Reporter organization: Corporate
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were assigned by Phoenix clearance; to fly the BXK3 departure; Palm Springs transition and to climb via the SID. Tower cleared us for takeoff on runway 7Right. After our hand off from the tower to departure control; departure control asked if we had been given runway heading. I responded no we were flying heading 070. Departure asked again if we had been assigned runway heading. I again responded we were flying the heading of the assigned departure. Departure control assigned a new heading. After the second query the pilot flying responded on the radio asking for clarification. The pilot flying clarified we had not been assigned runway heading and that we had been assigned the BXK3 departure. There was no conflict with any other aircraft. Departure control responded there was some difficulty with the new SID procedures and the BXK three departure.


Second narrative: Departure PHX. Cleared BXK3. Tower cleared us for takeoff. Departure Control; changed our heading. We were flying assigned BXK3. Departure Control thought the Tower had assigned us a heading of 100 [degrees] the Tower had not assigned a heading.


Synopsis: CE560 flight crew reports being queried by PHX Departure Control about their compliance with the BXK3 Departure. The crew was flying a 070 degree heading past the point at which they should have turned to a 100 degree heading.
Date: 201204
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Fuel Line; Fittings; & Connectors
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Situational Awareness; Communication Breakdown; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Company Policy; Chart Or Publication; Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: This morning I; a Maintence Manager; was waiting to board a company flight in the gate area when I observed an Aircraft Contract Fueler removing the bonding cable between the aircraft and the fueling hydrant cart BEFORE disconnecting the fueling hose from the aircraft. This is a safety related incident with a fairly high risk factor. It is also opposite to the required procedure of removing the bonding cable AFTER the fuel hose has been disconnected to avoid static electricity sparking at the fuel connection when the hose is removed.  Reference company Air Carrier Fueling Manual and FUEL form.




Synopsis: A Maintenace Manager observed Contract Fuelers not in compliance with company procedures during the fueling operations of a company A320.
Date: 202010
Local time of day: 0601-1200
Location: BWI.Airport, MD
Weather elements / visibility: Fog
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion
Second reporter function: First Officer
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Weather; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: The Jeppesen 10-9E Low Visibility taxi chart flow pattern does not concur with BWI Ground Control taxi charts. We contacted Ground Control before push and asked if we could expect Runway 10 instead of Runway 15R due to the flow pattern shown on 10-9E SMGCS Low Visibility chart. Taxiing to Runway 15R was against the directional flow pattern shown on Taxiway F. We explained our concern to the Ground Controller. This was not an option because their charts did not show Runway 10 for departure during low visibility operation from our position at the new Midfield Cargo Complex. Our charts show taxi available to Runway 10. We discussed this to our Dispatcher; Duty pilot and Ops. We requested a 'follow me' service provided by the airport to guide us safely though the low visibility to Runway 15R. [I suggest] a revision to BWI Ground control SMGCS (Surface Movement Guidance and Control System) Low Visibility taxi charts for departures to Runway 10 from Midfield Cargo Complex as shown on Jeppesen Low Visibility SMGCS chart 10-9E; [and also] change taxi flow direction for operation from Midfield Cargo to Runway 15R.


Second narrative: During pre-departure briefing; we noticed that SMGCS (Surface Movement Guidance and Control System) Low Visibility taxi chart for Runway 10 and Runway 15R; from our current position; we could only use Runway 10 for departure. I contacted BWI Ground to request Runway 10 for departure. BWI Ground responded that due to low visibility procedures in effect; Runway 10 was in use for arrivals and Runway 15R for departure and our taxi route would be [Taxiways] G; F; P to Runway 15R. I explained to him that according to the SMGCS chart we would be taxiing against flow on Taxiway F and we could taxi to Runway 10. Ground responded that he did not have charts for a low visibility taxi to Runway 10. We contacted Dispatch; Duty Pilot and Ops. We requested a 'follow me' to guide us to Runway 15R on the expected route and departed.[I recommend] BWI Ground update their SMGCS charts and establish a low visibility taxi route to go from Midfield Cargo to Runway 15R.


Synopsis: Flight crew reported a low visibility taxi chart discrepancy.