elihoole/asrs-aviation-reports huggingface dataset:
Date: 202001
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: The new company tracking system went into live production which slightly altered the procedures outlined in our procedure manual. ZZZ Stores Management issued a Memorandum providing additional directives on how to complete the Air Waybill and dictated which COMAT shipments would be assigned AOG status and which would be assigned Must Ride status which superseded the procedure manual. An additional Memorandum was issued from ZZZ Stores Management which required additional procedural guidelines to make 'Positive Contact' with Ramp personnel when delivering AOG COMAT Shipments further deviating from the procedure manual. These directives has caused the over abundance of AOG COMAT Shipments.ZZZ Stores Management mandated the deviation of published procedures COMAT Shipments. The Line Maintenance Management should issue a revision to the procedure manual as soon as possible; and in the mean time all Stores should adhere to the current policies and procedures listed to the fullest extent possible.




Synopsis: Reporter stated that new procedures at his station are causing excessive COMAT shipments on company aircraft and are not being tracked correctly.
Date: 201208
Local time of day: 1801-2400
Location: ZMP.ARTCC, MN
Aircraft: UAV - Unpiloted Aerial Vehicle
Operating under: Part 91
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZMP
ATC / advisory: Center ZMP
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Training / Qualification
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: While working an adjacent sector I witnessed a UAV deviate from his assigned altitude. This UAV was cleared to maintain FL350. The aircraft descended out of FL350 to FL300 without a clearance. When questioned by the controller; the remote pilot stated that he could not maintain FL350 so he descended. I feel this event happened due to the training of the remote pilots of the unmanned aircraft. I had no role in the event other than witness. I was informed by the controller and the FLM that they were not going to file any paperwork on the event. The accountability and standards for unmanned aircraft remotes should be equal to the standards of the commercial pilots. Also unmanned aircraft must be held to the same restrictions as manned aircraft. For example; in the Global Hawk System; if the aircraft loses data link it will fly its programmed flight plan. It will not maintain its last assigned altitude. In this example positive separation can not be maintained.




Synopsis: ZMP Controller reports a UAV descending out of FL350 to FL300 without clearance. When questioned by the Controller the remote pilot stated that he could not maintain FL350 so he descended.
Date: 201707
Local time of day: 1801-2400
Location: SCT.TRACON, CA
Aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Time Pressure
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Training in progress. Aircraft was on arrival into SNA at 080. We issued a descend clearance to 060 and speed of 190kts. Aircraft read back '60 to a 190'. Aircraft then turned to a 190 heading directly into an MVA of 079 descending out of 080. The proximity of the boundary line to the arrival was less than 1 mile; given us not time to fix the situation until it was too late. We observed the turn and issued a stop descend; low altitude alert; and climb back to 080 immediately. Be more vigilant in verifying the correct read back when doubt occurs because of the proximity of the higher MVA.




Synopsis: SoCal TRACON Controller reported a bad readback from a pilot which caused an instantaneous airspace violation.
Date: 201808
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class B ZZZ
ATC / advisory: Ground ZZZ
Second aircraft: B737 Next Generation Undifferentiated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Situational Awareness; Communication Breakdown
Anomaly: Ground Event / Encounter Aircraft
Detector: Person Flight Crew; Person Ground Personnel
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Evacuated; General Flight Cancelled / Delayed
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After pushing back from [the] gate we received our taxi clearance from outbound Ground Control. With both engines running we started our turn towards [the] taxiway with no wing walkers or guidance from ground personnel. As the FO in the right seat I had my head turned to the right clearing the area where we were about to taxi. Shortly after starting our forward movement I felt the airplane shudder and we immediately applied our brakes and came to a stop. After a short discussion with ground personnel it was determined we struck a parked B737 parked at [the adjacent] gate. The flight attendants reported smelling a fuel smell in the cabin shortly after we came to a stop. We notified Ground Control and requested the fire department investigate the fuel smell and examine the aircraft exterior. It was then determined we should not move the aircraft for fear of causing additional damage. The fire department then provided a set of air stairs and we deplaned the passengers via the 2L door without incident.




Synopsis: A320 First Officer reported striking a parked aircraft at an adjacent gate while taxiing.
Date: 202107
Local time of day: 1201-1800
Location: 3J1.Airport, SC
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial; Other TAIL WHEEL
Human factors: Troubleshooting; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Ground Event / Encounter FOD; Ground Event / Encounter Person / Animal / Bird
Detector: Person Flight Crew
When detected: Other takeoff
Result: General None Reported / Taken
Contributing factors: Human Factors; Environment - Non Weather Related; Airport
Primary problem: Environment - Non Weather Related

Narrative: Airport operations. While operating at this airport (Ridgeland SC) 3J1 the taxiway and runway markings are obscured by tall grass. Grass has grown to two to three feet and it is hard to see the markings and the airport now is being overrun with wild dogs and coyotes as well as deer. This airport was recently improved with new runway and grass areas however the airport management has chose to not maintain safe operations of the facility. My plane used to use the grass runway adjacent to the hard surface and now is unusable as the grass has grown too high making visibility restricted. My prop comes in contact with the taller grass. Please look into this for the safety of based aircraft and visiting aircraft as approaching the airport you can't tell the height of the grass from the air and we don't need wildlife entering the runway environment.




Synopsis: Pilot reports the condition of runways and airport facilities are falling into disrepair. Pilot states grass runway conditions are becoming unsafe for landing aircraft because the grass has grown too high.
Date: 202101
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: Tower ZZZ
Aircraft component: Fuel System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Fuel Issue
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: In the climb; an amber fuel imbalance was noticed on the fuel quantity indicator. The appropriate checklists where done to determine the source or why the imbalance [occurred]; that was not present before or during takeoff. It was later monitoring the fuel; that we [realized we] might [have] a possible fuel leak. The [projected] fuel at destination [continued to decrease]. The fuel over enroute fixes was also 1;000 lbs less than planned. After a safe landing back [departure airport]; the center fuel tank had approximately 2;300 lbs of fuel and the right center pump low pressure light illuminates; which only illuminates when failure occurs or little or no fuel on the center tank. Aircraft was parked at the gate safely without further events.




Synopsis: B737-800 First Officer reported returning to departure airport after experiencing a fuel imbalance and possible fuel leak.
Date: 201904
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Student
Human factors: Situational Awareness; Training / Qualification
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: When landing on Runway XX; my aircraft bounced; and when I touched the ground the second time; the aircraft veered to the left side of the runway. When I knew I was headed for the grass on the side of Runway XX; I first attempted to apply right brake and rudder to place me back towards the center line; and when I realized I was too crooked to get back to the runway; I had to apply left brake and rudder to avoid hitting a runway light; which caused me to enter the grass on the side of the runway. After this; ATC was notified that I was stuck in the grass beside the runway; in which aircrafts were held in the pattern; and on the ground; until the ZZZ Fire Department was able to come help me get the plane out of the grass; and off of the runway. Aircraft sustained no damage.




Synopsis: Student Pilot reported bouncing on the runway; losing control of the aircraft; and ending with a runway excursion into the grass.
Date: 201701
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Challenger CL604
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Flight phase: Taxi
Reporter organization: Corporate
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: Taxi
Result: General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The crew performed an emergency evacuation on the taxiway due to smoke and fumes in the cabin and cockpit. All three crewmembers smelled the fumes that appeared to originate in the aft cabin area. The crew stopped on the taxiway and reported the fumes to Tower. The crew requested Crash Fire Rescue (CFR) as a precaution. After CFR inspected and found no 'hot spots' in aircraft the crew requested the aircraft be towed to [FBO]. Due to the emergency evacuation the emergency lights activated and could not be turned off. A maintenance discrepancy was entered in the logbook for the smoke and fumes along with the emergency light activation. None of the crewmembers reported any breathing problems and declined to go to the hospital.




Synopsis: CL604 Captain reported the three crew members evacuated the otherwise empty aircraft on the taxiway when they noticed smoke and fumes.
Date: 201603
Local time of day: 1801-2400
Location: ZZZ.Tower, US
Flight conditions: Mixed
Weather elements / visibility: Cloudy
Light: Night
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Climb
Airspace: Class D ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter VFR In IMC; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Undergoing an instrument proficiency check with a CFII. ATIS called for BKN045. Shortly after takeoff; I put on a view limiting device and instructor assigned headings and altitudes for training purposes. Climbing through 3;000 feet MSL; I looked out the side window and saw we were in solid IMC. I asked my instructor if we should call ATC and pick up an IFR clearance or descend back below the clouds. He said no and instead told me to fly a heading and altitude away from known terrain and obstructions; and then later we descended below the clouds to VMC once clear of known terrain; mostly relying on our onboard GPS.Knowing that the ceilings were relatively low; I should have insisted on doing the IPC under IFR on an active flight plan and clearance; but instead I trusted the instructor to keep clear of weather while I was under the hood. Also; once I noticed we were in IMC; I should have made a 180 degree turn and descended rather than trust the GPS for terrain and obstruction clearance.




Synopsis: The pilot of a C182 reported that while on a practice instrument departure with a flight instructor; the aircraft entered instrument conditions without an IFR flight plan.
Date: 202012
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Aircraft: Commercial Fixed Wing
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)
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Flight Attendant
When detected: In-flight
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Passenger X in [seat] XX1 brought his own alcohol. When I came by his row for drinks his mask was down; he was sleeping and he had an open can of mixed drink-whiskey and coke. I woke him up-asked him to mask up and asked him if he knew he couldn't bring his own alcohol on board. Mr. X nodded and I apologized but had to confiscate his drink. 3 times he was reminded of his mask and he grudgingly put it back up over his nose each time he was reminded. Upon landing he had his mask completely off and told the D FA that I ruined his trip. Alcohol brought on board and tried to be consumed.Mr. X may need a reminder for his trip back that he needs to comply.




Synopsis: Flight Attendant reported that a passenger brought and consumed their own alcohol during the flight. Flight Attendant reported that the passenger was not compliant with face mask policy.
Date: 201605
Local time of day: 0601-1200
Location: IAH.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Falcon 2000
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Climb
Airspace: Class B IAH
ATC / advisory: TRACON I90
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Situational Awareness; Training / Qualification
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: I was with an IOE student who came over to the DA-2Easy from [another aircraft] as a PIC. When you get [the] PDC on the [other aircraft]; the entire clearance is displayed on the screen.  In the Easy; because of the different screen; you have to scroll down to see the entire clearance. He copied the clearance on to the master document but didn't scroll past the squawk.  So; when we briefed from what he wrote down; it read 'climb via SID'. The top altitude is 16;000 ft.  So; that is what I set in the altitude alerter. To complicate matters; the passengers showed up 40 minutes early. After takeoff; climbing through 5;300 ft; ATC asked what altitude we were assigned. The pilot responded '16;000 ft.' ATC said we were supposed to 'climb via SID; except maintain 5;000 ft'. ATC then told us to continue climb to 16;000 ft. Once we got above 10;000 ft; I brought up the AFIS page with the PDC. I scrolled through to the bottom where it reads 'end of clearance'. It did read 'climb via SID; except maintain 5;000 ft.' When getting a clearance via PDC; make sure to scroll through until you see 'end of clearance'. Another option to enhance safety would be to install a printer; so we can print important information from the AFIS.




Synopsis: Falcon 2000 Captain reported an altitude overshoot after misreading a PDC because they failed to scroll down to capture the final lines.
Date: 202010
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
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: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Confusion; Communication Breakdown; Distraction; Troubleshooting; Situational Awareness; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Company Policy; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: Lead FA brought to attention of flight deck crew that she had requested PPE and it was not delivered. We requested through operations that we needed PPE for FAs. Cockpit crew gave our bag of gloves to FAs while we waited. Gloves delivered to FAs; but were extra small and did not fit. Called Operations said they were all out of proper sized gloves and they were on back order. I advised Lead FA (she was upset) wanted to know name of station manager. I advised her to write [a] report and I would write report. No conflict with FA and cockpit crew.




Synopsis: Air carrier Captain reported flight attendants did not have correct sizes of Personal Protection Equipment to work safely.
Date: 201811
Local time of day: 1801-2400
Location: ZTL.ARTCC, GA
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb; Cruise; Descent
Airspace: Class A ZTL
ATC / advisory: Center ZTL
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Air Traffic Control Separated Traffic
Contributing factors: Company Policy; Human Factors; Staffing; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: I was working the D Side (Radar Assist) on when the Radar Controller having just had a loss while vectoring seemed to lose the flick. The controller in the few minutes after the event made several comments about not knowing how to proceed with positive control of the airspace and was visibly shaken by the event. I then told the Radar Controller a plan to regain positive control of the sector; but the controller took no action. I then; feeling it was the only way to recover the sector in a timely enough manner to avoid another event; took control of the sector. I moved from the D side to the Radar side and had that controller work my D side. Since on this night like most nights we were short staffed I felt that it would be safer and faster to do this rather than page someone back from outside the control room; who would need to monitor for precious moments to get the flick themselves before having to go through a briefing with a rapidly deteriorating traffic situation.Many things broke down throughout my session. I watched 2 Radar Controllers struggle through a rapidly changing and many times overly complex and deteriorating traffic situation; with what seemed like very little help from surrounding sectors; centers; and traffic management. There seemed; at least from the trenches of the sector like there was little or no attempt by anyone along the chain of events to be proactive to prevent an unsafe situation.




Synopsis: Center Radar Assist Controller reported assuming the Radar Controller position when the Radar Controller lost situational awareness.