elihoole/asrs-aviation-reports huggingface dataset:
Date: 201901
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A321
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: Recirculation Fan
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During cruise flight; smoke was reported by flight attendants coming through the forward part of the galley floor behind the carts. [Notified ATC] and diverted to ZZZ for maintenance. [Maintenance logbook] entry made and [report] form filed. Mechanical malfunction and failure of a recirculation fan; per maintenance tech after arrival.




Synopsis: A321 Captain reported smoke emanating from galley floor and diverting.
Date: 201505
Local time of day: 1801-2400
Location: PVD.Airport, RI
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 152
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class C PVD
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot; Captain
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness; Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Landing Without Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: In the afternoon; I took off [onboard a] Cessna 152 and intended to fly to SFZ. After takeoff for about 5 minutes; the GPS connection failed. I tried several times to reset the GPS but it did not help. Then I started to circle the aircraft and the GPS went back on for another 3 minutes. After I realized that the GPS was OK again; I made up my mind to fly to SFZ. While on route; the GPS failed again until I accidentally landed at PVD; which is a Class C airport. Even after I landed; I still believed that I landed at SFZ. Contributing factors; flying the aircraft without flight watch; which is important in navigating the flight. I reset the GPS but it did not help.Perceptions; judgments; decisions: at first I circled the aircraft; which was [the] right decision and performance; but I did not try to fly back to the based airport; which can prevent the event from happening. So bad decision based on GPS failure situation.I believe that in the future days; if the GPS fails again; I should first try contacting flight watch service and if necessary fly back to the based airport or closest airport instead of 'just go'.




Synopsis: Single engine Cessna pilot experiences a GPS failure on a flight to SFZ. After circling for a few minutes the GPS begins to function again and the flight is continued with a second failure occurring closer to SFZ. PVD airport is mistaken for SFZ and a landing ensues without contacting the Tower.
Date: 201202
Local time of day: 0001-0600
Location: PDX.Airport, OR
Flight conditions: VMC
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Contributing factors: Aircraft; Chart Or Publication; Procedure
Primary problem: Ambiguous

Narrative: During preflight it was noticed that the Engine Out SID for PDX 10L in the FMC is different than the typed Engine out SID given to the flight crew prior to departure as well as the description and the pictorial on the special procedures pages for this airport.  The FMC shows a left turn to 290 degrees instead of a right turn shown by both the pictorial and the written word.  Runway 10R is supposed to have the left turn.  Please audit the FMC data and change it if necessary.  This EOSID will present itself to the crew in the event of an engine failure and if activated by the crew can and will create confusion at a critical time.  They may also not have the performance for terrain clearance.




Synopsis: Air Carrier Captain discovers that the Engine Out procedures for PDX; stored in the FMC are different from the printed procedures issued by the company.
Date: 202003
Local time of day: 0601-1200
Location: D01.TRACON, CO
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B DEN
ATC / advisory: TRACON D01
Second aircraft: Commercial Fixed Wing
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Distraction
Second reporter function: First Officer; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Vector put us inside DRUMM intersection which was 9;000 ft; MSL to be on path. We were given 'Maintain 9;000 ft. until established; cleared ILS Runway 35R.' At that time; we talked about Aircraft Y landing in front of us and the need to maintain one dot high for wake turbulence. We also had a decreasing headwind which necessitated a lower power setting that we also talked about. We configured early to regain the glideslope from maintaining 9;000 ft. until established. The Pilot Flying asked for flaps 40 to help be in the slot. Concentrating on Aircraft Y that landed in front of us; I failed to crosscheck the altitude when he asked for flaps back to 30 until I moved the flaps. At that time; we were at 402 ft. AGL. I should have directed a go-around at that time. Lesson learned.


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


Synopsis: B737-700 flight crew reported landing from an unstabilized approach to DEN.
Date: 201207
Local time of day: 0001-0600
Location: ZLC.ARTCC, UT
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZLC
ATC / advisory: Center ZLC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Second reporter function: Enroute
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I received a position relief briefing from the previous Controller. He had accidentally dropped the track of Aircraft X instead of the intended arrival; but didn't realize it. At the time I signed in to take the sector; the limited Data Block of Aircraft X was at the boundary leaving my airspace and I didn't notice it. I remember Aircraft X calling me later to ask for a higher altitude. I did not remember working him; so I pulled up his Flight Plan and ran a route line to see where he was. The route line came up in the middle of the adjacent sector's airspace; and I saw the call sign in the limited Data Block next to the route line; so I sent him to that sector's frequency (Sector 16). Since dropping a Data Block is so easy to do and can cause such an unsafe condition; it might help to make dropping Data Blocks have the same procedure as removing a flight plan; where a /OK entry is required. Perhaps many people just /OK without really double-checking; but it might save some people from making a mistake.


Second narrative: I was working Aircraft X. I had 2 aircraft on approach at BZN: Aircraft Y; a B757; followed by Air Carrier Z; a CRJ; both on the visual approach. BZN Tower called with a downtime on both aircraft just as Aircraft X was over BZN field and I accidentally dropped Aircraft X and Aircraft Y's tracks. A few moments later I looked back and noticed that Air Carrier Z's track was still there and dropped it. I remember thinking that I thought that I had already dropped the track and I should go back and recall my entries to see what I had actually typed but then I was distracted with another BZN departure and forgot to investigate. I began my position relief briefing and failed to notice the code a few miles from the boundary of Sector 16. When new Controller [came on] the aircraft was just crossing the boundary. I needed to follow through and pay better attention.


Synopsis: ZLC Controller described an airspace incursion event immediately after assuming the position.  Reporter noted that the previous Controller had unintentionally dropped a data tag causing the incident.
Date: 201606
Local time of day: 1801-2400
Location: ORD.Airport, IL
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
ATC / advisory: Tower ORD
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Human-Machine Interface; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: ATC Equipment / Nav Facility / Buildings; Human Factors; Procedure
Primary problem: Procedure

Narrative: Aircraft X was instructed to Line Up And Wait on Runway 28R. After issuing a takeoff clearance; the pilot advised he had 'red lights'. I then instructed the aircraft to hold in position and rescanned the runway at which point I noticed an unidentified vehicle crossing at taxiway 'F' moving in a southbound direction. After verifying that there were no further conflicts; I then once again cleared the aircraft for takeoff.RWSL [Runway Safety Lights] worked as intended in this instance; recommend installing this safety feature in all runways at ORD.




Synopsis: ORD Tower Controller reported clearing an aircraft for takeoff. Pilot reported they had 'red lights on the runway'. Controller advised pilot to hold position and observed an automobile on the runway. After vehicle was cleared aircraft was given takeoff clearance again. Controller liked the fact that the Runway Safety Lights Worked.
Date: 201705
Local time of day: 1801-2400
Location: SAN.Tower, CA
Light: Dusk
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground SAN
Second aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Reporter organization: Government
Reporter function: Other / Unknown
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification; Workload; Confusion; Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: Ground had coordinated to cross Aircraft X behind Aircraft Y at Bravo 4. Aircraft Y was on a 1.5 mile final and Aircraft X was approaching Bravo 6 and ground told Aircraft X to cross the runway at Bravo 4 while Aircraft Y was still on a 1 mile final. I said 'No!' Since aircraft had not passed the intersection yet and was still in the air. Controller said; 'It's OK because she said Bravo 4.' I assume they are using the anticipated runway separation.I tried to get clarification if this is allowed but do not have an answer. It seems to leave a lot of room for error/runway incursion. Aircraft X could have crossed at Bravo 6 since they cross there half the time; thinking it's what controller meant since there was someone on final or Aircraft Y could have tried to speed up to cross at Bravo 4 before the landing traffic etc. I would like clarification/reference in 7110.65 where either you are allowed to or when you are [not] allowed to say cross. We have had a lot of briefings on runway incursions but maybe reiterate when you are permitted to start an aircraft to cross. It seems to be a widespread problem here that controllers say cross way too early; when landing or departing aircraft are still a whole intersection from reaching the crossing point.




Synopsis: SAN Tower Controller reported confusion with guidance on issuing crossing clearance to aircraft too early.
Date: 201705
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain; 5
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Pneumatic System Control
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: Prior to takeoff I requested the windshield wipers be turned off at gear up. Crosswind at takeoff. Captain tried to turn off FO windshield Wiper; but failed. Requested heading received. Between 400-1000 ft Bleed 1 followed by Bleed 2 failed. Bleed overpressure followed by multiple other lights. I never had a chance to say Identify cancel before the Captain had the QRH out. Captain requested straight out departure to 5000 and did not declare an emergency. Captain did not follow the normal takeoff actions and call outs per SOP procedures.




Synopsis: ERJ-170 First Officer reported a dual bleed failure during climb out and the Captain did not follow normal takeoff actions nor call out SOP procedures.
Date: 201207
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Prior to shutting down the right engine I noted the forward cargo 'open' light illuminated. [We] immediately shut down the right engine. This is the second time within a month that a ground worker at the airport has walked in front of an operating engine. It is extremely dangerous to do so.




Synopsis: B737-800 Captain reports the forward cargo open light illuminated after gate arrival with the right engine still operating. The engine is immediately shut down.
Date: 202009
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Gulfstream G280
Operating under: Part 91
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter function: First Officer; Pilot Flying
Anomaly: Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: After receiving clearance for the VOR approach; we were unable to see the airport environment due to smoky conditions. The plane was flown in accordance to the approach; but by the time we could see the runway; we were unable to execute a stabilized approach; so we conducted a go-around.




Synopsis: G280 First Officer reported executing a go-around after not being able to perform a stabilized approach due to the smoky conditions of the airport.
Date: 202006
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: UAV - Unpiloted Aerial Vehicle
Flight plan: VFR
Mission: Photo Shoot / Video
Flight phase: Takeoff / Launch
Reporter organization: Government
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Private
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Airspace Violation All Types; Conflict Airborne Conflict
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: [We were] requested to fly to map the perimeter of the fire. PIC was informed that the TFR was in place and clearance was issued to launch. The aircraft was launched and began to climb to its mission altitude.Within minutes of takeoff traffic was observed inside the boundary of the TFR. Since this was not expected the crew and PIC took measures to avoid conflict with the traffic and made slight adjustments in course and altitude to avoid. Positive visual separation was achieved with the use of a ground observer and the UAS camera system.Once conflict was mitigated further effort was made to determine if an incursion had occurred. It was identified that an error was made and that the TFR was not activated as claimed. Immediate recovery of the UAS was conducted and the aircraft was safely landed at the intended landing site. In order to correct and avoid another instance of this event we have implemented a procedure to confirm valid activation of the TFR before every flight operation is conducted.




Synopsis: UAV operator reported a TFR miscommunication that resulted in an airborne conflict with an aircraft.
Date: 201911
Location: ZZZZ.ARTCC, FO
Flight conditions: VMC
Aircraft: B787 Dreamliner Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Fatigue; Physiological - Other; Situational Awareness; Workload
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors; Weather
Primary problem: Human Factors

Narrative: At XA46 received CPDLC (Controller Pilot Data Link Communications) clearance to deviate +/- 25 NM for weather. At approximately XB05; [we] returned to centerline to split two thunderstorm cells; but verbalized; 'We're back on course; but don't report back on course as we're still needing to deviate.' I do not recall if PNF (Pilot Not Flying) acknowledged my comment; but I believed he understood. At about XB07; PNF workload suddenly became high as we had just crossed the FIR (Flight Information Region) and he was accepting the ZZZZ login and PNF said; 'I'll make the position report.' He apparently also reported 'Back on course;' though he did not recall for certain and the PF (Pilot Flying) did not hear any comment to indicate that he had. There was crew change at approximately XB11; the Captain was briefed that we had clearance to deviate; and the other PNF left the cockpit.At approximately XB20 we again deviated for weather as we believed we were cleared to do so and ZZZZ almost immediately sent us a message; 'I show you 3 NM right off course.' We again asked for clearance to deviate +/- 25 NM and received it; but upon checking the ATC downlink log; it became obvious that we had indeed reported 'back on course;' so it was our error. It was a minor deviation that was caught immediately; but it was a deviation.Fatigue was an issue as both the PNF and PF were tired due to circadian issues. PH was about 30 hours since full night's sleep but with about 2-3 hours sleep during 4.5 hour FAR117 prescribed break. Primary issue was imprecise communication and lack of verification leading to PF and PNF not being on the same page regarding the current clearance.




Synopsis: B787 First Officer reported deviating off course in cruise without clearance.
Date: 202112
Local time of day: 1801-2400
Flight conditions: VMC
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Human factors: Situational Awareness
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Too low on the final approach path to the runway over the terrain that surrounds final. Misinterpretation of charted altitude and where we were on final in correlation to distance. Approached terrain to level inside FAF below glideslope intercept altitude; descent was too steep given the geographic location; which set off the warning. All we had to do to correct was level off at the already preselected altitude; but shallow the descent. Visual terrain clearance was guaranteed at all times while in VMC conditions.[Reporter suggests] Ensure proper altitude at DME locations. Extend final to intercept glideslope at proper altitude. Request vectors for the ILS approach instead of taking the visual.




Synopsis: EMB-145 First Officer reported descent below published safe altitudes; resulting in terrain conflict alert.