elihoole/asrs-aviation-reports huggingface dataset:
Date: 201508
Local time of day: 1201-1800
Location: CPS.Tower, IL
Light: Daylight
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Operator: Air Taxi
Operating under: Part 135
Flight plan: VFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B STL
ATC / advisory: TRACON T75
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft X; a VFR inbound from the southwest; checked on the frequency upon transfer from ARTCC. Upon initial contact; I told Aircraft X that he was cleared into the Class B airspace; and to expect Runway XX; which was noted closed on the ACE-IDS. I then believed that I forced the data block on to the arrival scope in order to initiate a point out with the arrival controller. Having a few other aircraft that I was working; my attention was pulled away from completing the manual point out while attending to a number of other aircraft. Aircraft X reported the airport in sight; at which time I had him change frequency to Tower in order for them to sequence him into their arrival sequence. They turned Aircraft X on to a downwind heading and had him contact the arrival controller in order to be sequenced into the flow for Runway YY.The main issue I am aware of in this situation is that I completely forgot that Runway XX was closed; even though it was listed as such on the ACE-IDS and was briefed to me by the controller being relieved at the start of the shift. I should have ensured a manual point out with the arrival controller; since the aircraft would be entering his airspace; at which time he may have informed me that Runway XX was closed and would offer a different solution.




Synopsis: TRACON Controller assigned a closed Runway for landing to a VFR aircraft. Tower Controller corrected the instructions and coordinated with the TRACON.
Date: 201603
Flight conditions: IMC
Weather elements / visibility: Rain; Thunderstorm
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: I notified both management and the local operations center that there was a fast approaching thunderstorm. There seemed to be less than adequate concern. I then again expressed my concern; that the storm was at the airport boundary; 'headed straight for us'. The reply was 'we are going to evaluate the situation'. I then stated that the ramp [should] be closed; the reply was no that it did not need to be closed. Approx. 2 minutes later; there was extreme wind; lightning; and rain. The wind reached an approx. speed to 60 mph in my opinion. After the event; there were 2 [wide body] aircraft that had been damaged by runaway containers. There were a number of containers; carts; [and] dollies that had been moved by the wind. There were multiple reports of persons knocked down by the wind; myself included. This was an extremely dangerous situation that should never have happened because we reacted after the fact; instead of being proactive before the event.




Synopsis: An air carrier ground employee reported some aircraft were damaged by high winds blowing equipment into them. The reporter stated the outcome would have been better if proactive steps had been taken while the storm was approaching.
Date: 201702
Local time of day: 0601-1200
Location: SFO.Airport, CA
Flight conditions: VMC
Weather elements / visibility: Rain
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B SFO
ATC / advisory: Tower SFO
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Captain; Pilot Flying
Anomaly: Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: Conditions high winds; rain; mist on runway from previous takeoff. Cleared for takeoff on 19R; and as we were airborne around taxiway G or H; don't recall; we noticed the tail of the previous landing aircraft was hanging well past the hold short line of the runway. In other words; they had stopped with tail infringing on space of runway. Due to distance; wind/rain; we could not tell this from our position while on the runway waiting for takeoff. Due to the angle/parallax; I doubt tower could tell how significant the incursion was from their position either. I would guess the last 1/4 of the tail was past the hold short/incursion bar.


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


Synopsis: B737 flight crew reported a takeoff from SFO with limited visibility. When airborne they noticed an aircraft that had been cleared to cross the runway before their takeoff had not fully cleared the runway.
Date: 201912
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Second reporter function: Flight Attendant (On Duty)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Flight Deck / Cabin / Aircraft Event Passenger Electronic Device; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Passenger
When detected: In-flight
Result: General Maintenance Action
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: Pax brought a stuffed animal to the aft and explained that the battery pack was hot. I turned it over and looked and I saw that the battery and it's case were melting. At this time [another Flight Attendant] happened to be walking back with trash. I told her to grab me the BCB (Battery Containment Bag). I called the pilots immediately. We put the stuffed animal in and followed protocol via the manual. I didn't  feel safe landing with the BCB at my feet. So I put it in the lav. We landed with the BCB with suspect device in the aft lav. When we landed the Captain came and took the BCB with the suspect device off of the aircraft. At this point the Captain made calls and said it was okay to take the suspect device out and return to the owner who wanted it back. They were very happy to get it back and I said to be careful and remove the battery pack from the stuffed animal. In the future I think we need more information on the procedure with the BCB. This doesn't happen often; but when it does we need to know what to do with the after math so everyone is not confused.


Second narrative: I was taking garbage from the front to the back and found [the other Flight Attendant] with a guest who had a stuffed reindeer. The reindeer had batteries which were hot to the touch and appeared to be melting. She asked for the BCB (Battery Containment Bag) and we put the reindeer in and informed the pilots. She put the bag in the Lav instead of the aft galleys door because she felt safer that way when landing. After landing the pilots made some calls. The family waited because they wanted the reindeer back which CA (Captain) said we could give back.When the pilot came out of the flight deck he asked what my manual said to do next; I told him my manual said to wait for instructions from the pilots; maybe there was something we missed or some information that could be communicated better to both sides on what to do after landing.


Synopsis: E-175 Flight Attendants reported the Battery Containment Bag (BCB) procedures are in need of additional information regarding the handling and disposition of BCB after landing. This BCB procedures deficiency became apparent after dealing with an electronic device's hot battery.
Date: 202105
Local time of day: 1201-1800
Location: SNA.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Medium Transport
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class E SCT
ATC / advisory: TRACON SCT
Reporter organization: Personal
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Coming in on the OHSEA2 arrival we requested the visual to 20R into SNA. Passing over BHEAR waypoint we were asked if we had an arriving aircraft in site that was inbound from the east; I believe on the Disney4 arrival. We visually acquired the aircraft and was told to descend to 4;000 feet MSL just to the east of BHEAR. We were then told to turn right heading 030 and asked if we had the aircraft in site and we said 'yes; in site. We were told to continue the right turn to 120 and then told we were cleared for the visual approach Runway 20R. When we were coming around at 4;000 feet MSL I realized we had been vectored inside of LEMON. I had to make an aggressive descent in order to capture the Glide Path to be stabilized by 500 feet AGL in order to have a normal descent rate with approach power and approach speed captured. During this aggressive rate of descent to capture glide path (estimated over 2;000 feet FPM); Tower made an advisory call 'low altitude warning; check altitude;' we were actually above glide slope and coming down onto Glide path when Tower made this call but the steep descent rate triggered their warning system and they made a radio call for a 'low altitude warning;' we were never below glide slope/glide path.The most important take away is that this whole scenario started because SoCal approach vectored us high and turned us tight inside of LEMON. This high and tight turn is very hard to capture a stabilized approach. I would recommend that SoCal gives additional downwind distance prior to turning base leg if the requirement is to stay above 2;500 feet MSL when turning near LEMON or HUKEM."




Synopsis: Corporate Captain reports low altitude warning from ATC during approach to SNA airport.
Date: 201905
Local time of day: 0001-0600
Location: LGA.Airport, NY
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Flight plan: IFR
Flight phase: Other Preflight planning
Airspace: Class B LGA
ATC / advisory: Tower LGA
Aircraft component: Oxygen System/Crew
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: During the flight deck preparation the aircraft crew oxygen test [revealed] that the 1250 psi display would drop to 200 psi when tested. The maintenance remedy was to open the oxygen valve correctly. When the demand of a simple push to test occurred the value was not capable of supplying oxygen. A call to [Maintenance] could not determine when the last time the oxygen was serviced or for how long [this was a] problem.




Synopsis: B737NG Captain reported pre-flight inspection revealed the crew oxygen system bottle valve was not properly opened.
Date: 201505
Local time of day: 0001-0600
Location: JFK.Airport, NY
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; Captain
Anomaly: Conflict Ground Conflict; Less Severe; Ground Incursion Runway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: On approach to runway 13L at JFK; at approximately 1;000 feet; long after we had been given clearance to land; an A330 aircraft crossed the runway at the approach end necessitating a go-around.  The aircraft was being towed across the runway.  The tower controller directed a go-around just a we had decided to go-around because of the conflicting aircraft.  We asked the controller who authorized the aircraft to cross in front of us; but he didn't know who the aircraft was talking to.  We executed the go-around and landed uneventfully on runway 22L. I believe it is obvious that the tower controller needs to be the person that authorizes aircraft to cross an active landing runway--- not someone that is unaware of the landing traffic.


Second narrative: We were cleared to land Runway 13L referencing an A-320 ahead of us. I had the landing traffic in sight and was concentrating on their clearance of the runway. About 300 feet AGL I told the First Officer (FO); who was flying; to continue; being certain that the previous aircraft would be clear before our touchdown. The FO questioned me and as I was saying 'yes; they are clearing' he initiated a go-around just as Tower called 'Go-around.' I looked at the landing zone to see an A-330 being towed in front of Runway 13L. The tail was dead center on the runway as we went around.Be sure taxiing/towing aircraft talk to tower before transiting the approach end of any runway. They should be on tower's frequency so aircraft can identify them and where they are in relation to the runway.


Synopsis: B737 flight crew executes a go around at low altitude as an A330 under tow crosses the runway in front of them. The Captain does not initially detect the incursion as he is watching to insure that the aircraft landing ahead has cleared the runway.
Date: 201210
Local time of day: 1201-1800
Location: DCA.Airport, DC
Flight conditions: VMC
Aircraft: EMB ERJ 135 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class B DCA
ATC / advisory: TRACON PCT
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: ATC Equipment / Nav Facility / Buildings; Chart Or Publication; Aircraft
Primary problem: Ambiguous

Narrative: During our descent on the FRDMM ONE RNAV Arrival; just past WLLLL; the Controller asked us whether we showed ourselves on course for the arrival. I verified that the autopilot was engaged; it was coupled to the right side; and that the First Officer was navigating in pink needles with the lateral mode set to NAV. Everything was set up correctly and the MFD depicted us as on course. I then responded that we did show ourselves on course. The Controller then informed us that previous company flights; as well as ours; had been flying up to a mile off course and had been rejoining the arrival more precisely at SEPII. He explained that; to him; it looked like our planes were flying the course depicted on the ELDEE 5 RNAV Arrival. I asked the Controller if he could tell me at what point our plane started to fly off course; but he stated he was not sure. He stated that he would try to figure it out with the next inbound company flight. We continued on the arrival with no further incident.




Synopsis: ATC advised an ERJ flight crew descending via the FRDMM RNAV STAR into DCA that their track (as well as that of several previous 'company' flights) between WLLLL and SEPII deviated about a mile before rejoining at SEPII. The flight crew advised their FMS displays showed them on course with the autopilot engaged in the NAV mode.
Date: 202010
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: Mixed
Weather elements / visibility: 6
Light: Daylight
Aircraft: PA-46 Malibu Meridian
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
ATC / advisory: Center ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: While cruising at FL180 enroute from ZZZ to ZZZ1 under control of ATC an unknown foreign object impact the pilot windshield fracturing the out glass layer. The windshield remained intact. I [advised] to ATC and requested vectors to the nearest suitable airport ZZZ2. An instrument approach was required with an uneventful landing. The incident resulted to no injuries to the pilot or passenger onboard. The unknown foreign object appears to possibly been some form of space debris for at the time of the incident the aircraft was not near any convective activity nor was the it experiencing any other weather phenomenon.




Synopsis: PA46 single pilot reported an uneventful diversion due to an in-flight encounter during cruise with an unknown object resulting windshield damage.
Date: 201708
Local time of day: 1201-1800
Location: SJC.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Bonanza 36
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: Tower SJC
Second aircraft: Commercial Fixed Wing
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Anomaly: Inflight Event / Encounter Wake Vortex Encounter
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Procedure
Primary problem: Ambiguous

Narrative: Landed short of threshold on Runway 30R due to encountering turbulence from preceding large aircraft.




Synopsis: Beech 36 pilot reported landing short of the threshold on Runway 30R at SJC after encountering wake turbulence from the preceding large aircraft.
Date: 202007
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent; Initial Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Human Factors; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: We were cleared direct ZZZZZ and the ZZZZZ3 STAR arrival at ZZZ. Quiet cockpit as we descended; Approach Control was very busy working two radios and had weather affecting departures. Passing 10;000 feet we got a call on guard asking us to contact Approach on a different frequency. The new Controller asked why we did not switch frequencies sooner. We replied that we had not heard our call sign previously and the other Controller was working two frequencies. Approach Control then asked which runway we expected. We told Controller XXL. Upon landing we were told to call TRACON. TRACON told me no traffic separation problem had occurred. TRACON asked me if we had been assigned Runway XX left or right. I told Controller I believe we were told to expect XXL but had not been assigned a runway by the first Controller. We landed uneventfully. Cause - ATC was working departures around weather and arrivals on two frequencies. TRACON informed me they were short staffed because of COVID. We the aircrew failed to query ATC to get assigned a landing runway which would affect the STAR. Suggestions - Increased involvement by ATC and aircrew is needed during manning shortfalls and a rapidly changing environment


Second narrative: [Report contained no additional information.]


Synopsis: Air carrier flight crew reported a communication issues with TRACON Control during arrival. TRACON was working departures and arrivals on two frequencies. ATC informed the crew they were short staffed due to COVID-19.