elihoole/asrs-aviation-reports huggingface dataset:
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: Marginal
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Human Factors; Procedure; Weather
Primary problem: Airspace Structure

Narrative: Aircraft X departed ZZZ on the ZZZZZ departure towards ZZZZZ1. There had been 2 departures prior to the aircraft that had to deviate below my Minimum IFR Altitude for weather on the departure procedure. Before the Aircraft X departure; the D-Side had called the tower and told them that the other departing traffic had to deviate below the Minimum IFR Altitude; and recommended that Aircraft X wait on the ground; but ended up releasing the Aircraft X aircraft.  Aircraft X checked on and requested a deviation out of 9500 feet. The ZZZ radar had been out of service prior to this departure; but must was returned to service just as Aircraft X was departing at I was able to ID him out of about 8500 feet.I informed the pilot that I could not give a vector until he was out of 11000 or 12000 feet. When the pilot was above the terrain I started to give vectors to the N-NW; trying to keep the pilot in a low Minimum IFR Altitude; but also avoiding the weather. At one point I gave the pilot a 330 heading; which turned him into my 14700 foot Minimum IFR Altitude; when they were at 14100 feet. I realized my mistake and issued a low altitude alert and told the pilot to expedite the climb through 14700 feet. He responded that he was already climbing through 14700 feet. I let the pilot continue to climb above remaining terrain on the 330 heading and then turned him on course. Training was in progress on the d-side during this event. Don't depart aircraft when there is weather in the departure corridor. Give ZZZ Tower a tower radar display so they can have weather depicted to them.




Synopsis: A Center Controller reported they vectored an aircraft below the Minimum IFR Altitude while trying to assist them in avoiding weather.
Date: 201412
Local time of day: 1801-2400
Location: ABI.Airport, TX
Flight conditions: Marginal
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class C ABI
ATC / advisory: Tower ABI
Second aircraft: Small Aircraft
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification; Confusion
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Weather was marginal so ABI was doing Localizer approaches to 17R; 17L is closed for construction.  I was CIC; traffic was very light.  The local controller; had Aircraft X on a 3-4 mile final 17R cleared to land and Aircraft Y calling off 82TS; a private field 2NM NE of ABI; requesting touch and goes.  The controller's response to Aircraft Y was this; 'Make ah...enter a left field...mid ah...left mid downwind for the left ah...downwind'.  Controller is not looking out the window and not watching the traffic; Aircraft Y turns west for a base to 17R and I had to tell the controller that Aircraft Y is cutting off Aircraft X.  She turns around and now sees the situation and turns Aircraft Y right to heading 360; right toward the traffic.  Aircraft Y immediately reports the traffic on final in sight and request a clearance for a Localizer approach instead of VFR pattern work.  Even though separation was not lost and only because I brought it to her attention (1 mile at best); this was an unsafe situation brought on by the local controller's lack of attention; awareness and knowledge.  These kind of situations are occurring on a daily basis.  Management is being made aware; but the unsafe events continue.                     Remedial training on maintaining awareness while on position; on how to sequence aircraft and how not to; and/or proper phraseology to avoid confusing instructions.




Synopsis: ABI Local Controller almost had a separation loss due to not paying attention.
Date: 201908
Local time of day: 1201-1800
Location: BUR.Airport, CA
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZLA
ATC / advisory: TRACON SCT
Aircraft component: Flight Director
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Human-Machine Interface; Training / Qualification
Anomaly: ATC Issue 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 Advisory / Alert; Flight Crew FLC Overrode Automation; Flight Crew Returned To Clearance
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Human Factors

Narrative: We were on the SLAPP 1 SID which is a new BUR Departure which I've never flown before. We were following the lateral guidance on the SID; but were not being given the published altitudes. We were cleared to climb to FL 230; I dialed that in and was climbing in VNAV. I got somewhat distracted because I was entering the enroute winds. Since we were not cleared to climb via; it didn't remind me to look at the FMC to check for any at or below or at or above altitudes; I kind of just forgot about the lateral navigation part of the SID and assumed VNAV would keep me climbing to the altitude that I set in the window. Unfortunately; there was an at or below 190 restriction at JETHK which the Captain also didn't notice. The aircraft leveled off at 190 for probably 5 to 10 seconds and the Controller promptly became angry. He asked; in a voice that wasn't pleased; why we had leveled off. I immediately started a V/S climb to get it going and then noticed the JETHK restriction in the FMC. I deleted the restriction and went back to climbing in VNAV. The Controller told us that Company pilots were routinely having this problem and that we needed to get it fixed. We climbed uneventfully to the assigned altitude after that and had an uneventful remainder of the flight. I should have looked more closely at the altitudes on the SID when we were given an altitude that was not associated with what was charted. When I'm given a climb via clearance I always check the box to make sure I know what is going to happen; but I just forgot all about checking the published at or below altitudes to make sure the aircraft wasn't going to level off at something lower then we were assigned. It was a new SID that I was unfamiliar with; so I should have been paying even more attention.




Synopsis: First Officer reported FMC leveled for restriction of at or below on SLAPP1 SID resulted in failure to climb to ATC altitude assignment.
Date: 201709
Local time of day: 1801-2400
Location: ZZZZ.ARTCC, FO
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZZ
ATC / advisory: Center ZZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure
Primary problem: Airspace Structure

Narrative: Prior to going on scheduled break; we received notice from dispatch of possible closure of a FIR (Flight Information Region) facility. Dispatch suggested possible routed if; in fact; the airspace or facility was closed. Crew discussion; weather; planning; and fuel changes were points of topic. I personally queried [Center] twice of the status of FIR facility and airspace. They responded saying both were open. Our routing was uneventful thus far. As the Captain returned from rest; the crew brief included the conversation I had with Center confirming [the FIR]. Prior to departing the cockpit for rest; there was nothing from dispatch; ATC; or other aircraft confirming actual closures.




Synopsis: B767 First Officer reported that they received information of a possible Flight Information Region closure while in cruise.
Date: 201306
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: A109 All Series
Operator: Corporate
Operating under: Part 91
Flight plan: None
Mission: Passenger
Flight phase: Cruise
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Corporate
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument
Anomaly: Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: While flying a passenger from a private golf course to their destination and then returning to my point of origin with no passengers I encountered some sort of string (like kite string) in the rotor head of my helicopter.  I am not sure as to where the incident occurred as the string in the rotor head was not discovered until on the ground after shutdown.  At no point on my flight was I at any unusually low altitudes; most of the time I did have clearance from Tower to be at 1;000 feet or higher on the assigned helicopter routes.  The weather was clear and the visibility was unrestricted.  If it was a kite that I flew through it had to be flying extremely high.  As stated earlier; I did not see or hear anything unusual.  I did not experience any unusual control loads and the helicopter gave no indication that anything was tied up in the rotor. After shutdown of the aircraft back on the golf course I saw a small piece of string in the rotor head on my post flight walk around.  Upon climbing up to the top of the helicopter I discovered a few hundred feet of string tied around the swashplate.  I informed Maintenance and we began the process of inspecting the aircraft for any damage. I informed my passenger that there was going to be a delay for an undetermined amount of time and told him to find another means of transportation.




Synopsis: The pilot of an AW109 helicopter noticed string on the main rotor head during the post flight inspection.
Date: 201901
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: Citation Latitude (C680A)
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Fractional
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Inflight Event / Encounter Weather / Turbulence; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; Flight Crew Took Evasive Action
Contributing factors: Weather
Primary problem: Weather

Narrative: Severe turbulence encountered during arrival into ZZZ. At 36;000 FT and approximately .72M we encountered strong mountain wave type activity and a rapid uncontrolled descent. Autopilot came off and we were able to keep the wings somewhat level. Pilot flying was pulling back forcefully on the control wheel but we were still descending at 4000 ft/min. Pilot Monitoring deployed the speed brakes but speed kept increasing. Finally regained control after losing 4;000 feet of altitude.




Synopsis: CE680 Captain reported loss of aircraft control due to severe turbulence during cruise.
Date: 202111
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Yankee AA1
Operator: Personal
Operating under: Part 91
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Nose Gear Wheel
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Other Multi Engine Instructor
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Gear Up Landing
Result: Aircraft Aircraft Damaged; Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon takeoff the nose wheel tire fell off. This was made aware by a transmission from another aircraft on the field and was later verified by Tower by performing a low pass over the runway. Upon landing kept back pressure on the aircraft to slow down the aircraft as much as possible before the nose touchdown. Right before landing removed the mixture and turned off the Magnetos. This was to help reduce the chance of a fire; along with reducing the damage to the aircraft.




Synopsis: Grumman Yankee Flight Instructor reported that the nose wheel fell off on takeoff. The instructor took all the safety precautions to slow down the aircraft before the nose gear touched down during landing and immediately removed the mixture and turned off the magnetos.
Date: 201308
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Dash 8-400
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: MD-83
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Developmental
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was training a developmental on the Departure RADAR position (DR). We had an MD83 cleared for a visual approach to Runway 17R. DHC8 was being vectored to follow the MD83. The MD83 swung out to a very wide base leg which conflicted with the vector the DHC8 was given. The developmental issued traffic to the DHC8 who was leveling at 090 as the MD83 was descending through approximately 085. The DHC8 did report the MD83 in sight and was then cleared to follow the traffic on the visual approach. While all that was happening; PA32 was also being vectored to follow the MD83 and the DHC8. He was assigned heading 120 from the west of the final. While the developmental was trying to sort out the problem between the first two aircraft we allowed the PA32 to come very close to the DHC8. I don't believe their targets merged; but I'm not sure proper traffic was issued. We simply didn't take into account the probability that our MD83 would swing out to such a wide base. I had told the developmental to descend the DHC8; but I hadn't thought to make it clear that I wanted him to keep the DHC8 a thousand feet above the base traffic.




Synopsis: TRACON Controller described a conflict event between an IFR and VFR arrival when an air carrier initiated a wide base turn.
Date: 202012
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: Cruise; Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Workload; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: Pre-flight; In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Three passengers boarded with their masks down. I asked them to pull them up. When collecting trash; before door closure; I noticed passenger in XX4 mask down again.  I asked her again to pull up mask and advised of policy; she laughed at me; then mocked what I had said. I asked again if she would pull up mask. Then advised the Captain of the interaction since I had to speak to her twice while on ground. Passenger in YY3 had mask down for second time in cruise when I collected trash after service.  He claimed he was forgetful. XX4 passenger played the peek aboo game where she had mask down but each time I approached; before I reached her; would pulled it up. ZZ4 passenger asked me how many times I was going to ask him to pull up his mask. When deplaning; had mask down.




Synopsis: Flight Attendant reported three passengers would not comply with face mask policy.
Date: 201507
Local time of day: 0001-0600
Location: NCT.TRACON, CA
Light: Night
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZOA
ATC / advisory: TRACON NCT
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Confusion; Distraction
Anomaly: ATC Issue All Types; 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 Provided Assistance
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: [Aircraft X] was given descend via BDEGA1 arrival landing runway 28L; expect visual approach but turned on the 28R routing at CORKK.Already mentioned in prior reports related to this issue. I couldn't get my username and password reset yesterday due to a glitch with the reporting system; so I think we were on visual approaches; but we might have been closely spaced ILS's. Either way; it doesn't change the fact that we have pilots turning on the wrong routing's due to a garbage procedure.




Synopsis: NCT Controller reports of aircraft assigned one arrival; but turning towards another runway that was not assigned. Controller complains about the procedure they are using.
Date: 201307
Local time of day: 0001-0600
Location: LAX.Airport, CA
Aircraft: Helicopter
Flight phase: Cruise
Airspace: Class B LAX
ATC / advisory: Tower LAX
Second aircraft: B757-200
Reporter organization: Government
Reporter function: Other / Unknown
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I was working the helicopter position. Aircraft X called at the Coliseum; which is a normal reporting point and requested the Harbor Route Southbound. I gave Aircraft X clearance through the Los Angeles B airspace via the Harbor Route Southbound below 900 FT. I also issued the aircraft a beacon code as required by local directives. I however did not RADAR ID the aircraft or verify its altitude. I did not do this because it is a known issue that RADAR coverage to the East low level; especially on the Harbor Route is poor. I paid little attention to the aircraft that were on final; since this route is procedurally separated from the LAX final by crossing altitudes. The Local SOP only requires Wake Turbulence separation between heavy jets and B757 departures and traffic utilizing the shoreline and beach routes. At the moment separation was lost; I was generating and issuing a beacon code to another aircraft; which I cleared into LAX B. Aircraft Y flew directly over the helicopter at 1;800 FT; the helicopter was at 900 FT. 1.) The altitude of the Harbor Route [should] be lowered to 500 FT. 2.) The route [should] be shifted 2 miles east of its current location. 3.) Issue crossing restrictions to aircraft on the visual approach to LAX.




Synopsis: LAX Controller described a possible loss of Wake Turbulence separation between a non-RADAR identified helicopter and traffic on final; the reporter providing several suggestions to prevent future occurrences.