elihoole/asrs-aviation-reports huggingface dataset:
Date: 202110
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Time Pressure; Situational Awareness; Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Undershoot; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Aircraft; Environment - Non Weather Related; Human Factors
Primary problem: Ambiguous

Narrative: I was working arrivals to Runway XXR. Aircraft X initiated a go around short final. I issued them a turn to 240 and 9;000 feet as local center was departing and I wanted to give them room. Aircraft X read back the instruction but did not turn and leveled off about 5;400 feet. I instructed Aircraft X to turn further right heading 280 with no response. I issued multiple headings further and further to the northwest to avoid terrain and sometimes they would respond and sometimes they would not. I asked multiple times about their altitude and instructed them to climb however they flew level around 5;400 feet for about 5 miles. I was doing my best to turn them away from rapidly rising terrain as it became evident they weren't climbing; but may have still gone into a higher MVA southwest of the airport.I believe the flight crew was dealing with some type of malfunction or abnormality were talking to me was not their priority. In hindsight I could have issued a low altitude alert to try to alert the crew they need to turn and climb in a more timely manner.




Synopsis: TRACON Controller reported an aircraft went around; but then did not listen consistently to the Controllers instructions leading to a Minimum Vectoring Altitude violation.
Date: 201812
Local time of day: 1201-1800
Location: PHL.Airport, PA
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B PHL
ATC / advisory: TRACON PHL
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Human-Machine Interface; Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Chart Or Publication; Human Factors
Primary problem: Human Factors

Narrative: This is the second pilot deviation I have been involved in in the exact same location and altitude in two months' time. Aircraft X had been cleared to maintain 6;000 and direct to BOJID to resume the BOJID2 Arrival STAR. The aircraft was observed descending through 5;300 between the waypoints BOJID and HIFAL. The flight crew misread; as had happened before; the 4;000 Expect altitude charted at FERUS and began their descent as if they were issued a 'descend via' instruction and as if the FERUS altitude was a requirement and not informational only. Remove all 'expect' altitudes and speeds from this STAR.


Second narrative: Due to short flight time I briefed the PHL arrival on the ground as part of the departure brief. In the briefings I briefed expected altitudes as expected altitude; and briefed that were loaded in the box. We De-iced in ZZZ and then took off. Prior to descent I re-briefed the arrival and the expected altitudes and that they were loaded into the box. On the arrival at BUNTS and at 8;000 feet; ATC vectored is off the arrival to a 030 heading. They then descended us to 6;000 and at 7;000 feet direct BOJID intersection to resume the arrival. We had previously briefed and loaded in the box all expect altitudes on the arrival including the expect 4;000 feet at FERUS. At BOJID we mistakenly started down to meet the 4;000 restriction at FERUS. Approaching 5;000 feet Approach told us to level at 5;000 and informed us of our mistake. Landed 27R with no further incidents. Our mistake was to think the altitude at FERUS was a hard altitude; and that we were cleared to descend via the arrival. A contributing factor to the incident is that KPHL is not an airport that neither I nor the copilot normally flies into. Human error treating an expected altitude like a hard altitude. Altitude awareness on expected altitudes.


Synopsis: PHL Controller and flight crew reported altitude deviation during descent on the BOJID2 STAR.
Date: 201903
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Skyhawk 172/Cutlass 172
Operator: Other Flying club
Operating under: Part 91
Mission: Training
Flight phase: Parked
Reporter organization: Other Flying club
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Inspection Authority; Maintenance Powerplant
Human factors: Distraction; Training / Qualification
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown
Contributing factors: Human Factors; Aircraft; Procedure
Primary problem: Human Factors

Narrative: During engine installation; I failed to install cotter pin in throttle control attachment nut and bolt. During flight; vibration loosened the nut and it fell off allowing the bolt to also fall free and resulting in loss of connection of the throttle control at the fuel servo. The engine speed remained at 2100 RPM. The pilot aligned with the runway and used mixture to shut down the engine when reaching the runway was assured. A power off landing was performed and the aircraft was undamaged then towed to the maintenance area where I discovered what had occurred. We are in the process of modifying policies and procedures to prevent recurrences of this incident.




Synopsis: Maintenance Technician failed to install cotter pin on throttle control resulting in engine shutdown in flight.
Date: 201910
Flight conditions: IMC
Weather elements / visibility: Rain
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Communication Breakdown
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Vehicle
Detector: Person Ground Personnel
Result: Aircraft Aircraft Damaged; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Equipment / Tooling; Procedure
Primary problem: Procedure

Narrative: While moving [an] aircraft; the shear pin broke when the main gear struck the steel plates they rested on. Upon removing the tow bar; the push back began backing slowly to reposition and struck the cleaning van that had parked behind it. The aircraft beacons were on because we had not completed the move.




Synopsis: Ground Personnel reported shear pins breaking on tow bar; resulting in the aircraft striking a parked vehicle.
Date: 201603
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: FBO
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Aircraft component: Nosewheel Steering
Component problem: Improperly Operated
Reporter organization: FBO
Reporter function: Pilot Not Flying; Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Situational Awareness; Training / Qualification
Anomaly: Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Ground Strike - Aircraft; Ground Excursion Runway; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: My first flight [with this student was] a night cross country into an unfamiliar airport and terrain. Flew to airport; overflew the airport to check windsock; and made a teardrop entry to enter the left downwind for Runway 22. Once landed; student started to use both left and right rudder and brakes; airplane became unstable I asked for flight controls; but students foot was still on rudder and brakes and plane ended up sharply veering to the left into the dirt on the side of the runway. Airplane ended up receiving prop damage and right wingtip plastic broke and nose wheel looked slightly bent.




Synopsis: A flight instructor reported that the student pilot did not apply appropriate nose wheel steering and braking during landing rollout; which resulted in a runway excursion and minor aircraft damage.
Date: 202108
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ; Class E ZZZ1
ATC / advisory: TRACON ZZZ
Aircraft component: Oil Pressure Indication
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; Flight Crew Returned To Departure Airport; General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb out through 14;000 ft. we noticed an amber oil pressure low indication on #2 engine. I was the PF(Pilot Flying) so I took the radios while the Captain ran the Engine Low Oil Pressure checklist which then directed him to the Engine Failure or Shutdown Checklist. The oil pressure dropped rapidly to approximately 3 PSI and the oil quantity dropped to 0. The checklist directed us to shutdown the #2 engine. We [requested priority handling] and coordinated with ATC for vectors to air return via the ILS XXL to ZZZ. We completed all appropriate checklists and coordinated with Dispatch; the flight attendants; and gave a reassuring PA to the passengers. The approach and landing were uneventful. After exiting the runway we were met by emergency vehicles and inspected. No damage or abnormalities were noted so we returned to gate X. We elected to shutdown and get towed to the gate. Two maintenance ELB (Electronic Log Book) entries were made and the Captain coordinated with Dispatch and the Chief Pilot via phone.




Synopsis: B737 Pilot reported oil pressure problems with the number 2 engine; requested priority handling and returned to departure airport.
Date: 201703
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: 10
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Vertical Stabilizer/Fin
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Inflight Event / Encounter Bird / Animal
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Just before pushback one of our Ramp Agents came into the cockpit and showed me a picture of what he thought was a dent on the vertical stabilizer. I proceeded outside and checked to make sure there was a dent that I was looking at about three by two inches about 40 ft high (1.5 ft below the top of the vertical stabilizer). I called Dispatch and he passed me to Maintenance Control. I reported what was found. Maintenance Control informed me that there was a small dent already reported on that area. I told them this was not small and it looked like there was some damage to the aircraft. They told me to write it up and to call Contract Maintenance. Luckily we had two of our Mechanics at the Station. They came to the aircraft and were able to get close to the dent and take pictures. They called Maintenance and after conference with them they informed me that the checkup was going to take a few hours. I informed the gate agent and Dispatch and the flight was canceled. When and how the dent happened is totally unknown.


Second narrative: We swapped into this aircraft. I performed the walk around in moderate rain with overcast clouds. I did not note any defects. While taxiing to the Runway the Controller reported birds near the runway. We did not see any birds; and we reported that to ATC. We flew the first 15 to 30 minutes of the flight in rain. We had a normal landing at destination which was sunny with scattered clouds.While preparing to leave the gate for our return flight; a Ramp Worker came to the flight deck and reported that he noticed 'what appeared to be a hole at the top of the vertical stabilizer.' The Captain went outside to inspect the aircraft. He returned; and made a Maintenance writeup for what appeared to be a hole in the leading edge of the vertical stabilizer; approximately 1.5 ft from the top (about 40 ft above the ground). He called Maintenance Control with the writeup.Company Maintenance Techs happened to be present. They inspected the damage as best as they could; due to the height of the damage; and confirmed repair would be needed. The flight was canceled due to the required maintenance.


Synopsis: B737 flight crew reported they were informed of possible damage near the top of the vertical stabilizer. After maintenance examination; the aircraft was taken out of service.
Date: 201509
Local time of day: 0001-0600
Flight conditions: VMC
Light: Daylight
Aircraft: Gulfstream G200 (IAI 1126 Galaxy)
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Autopilot
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I wrote up Aircraft X for an autopilot disengaging in flight and stiff ailerons. We left RVSM airspace due to the autopilot malfunction. Ailerons resumed normal control forces descending into the 20's. As we had full controllability of the aircraft I view this as a non-reportable NTSB event.




Synopsis: G-200 Captain reported he wrote up the aircraft for the autopilot disengaging and 'stiff ailerons.'
Date: 202008
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Dusk
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Smelled something burning and alert sounded with low voltage annuciator. Took action by opening window; turning off non-essential electrical and ready to reach for fire estinguisher. Communicated with ATC letting them know about the burning smell and losing battery power. I asked for a climb and direct to ZZZ. Did not officially request priority handling but ATC asked if they should roll out the trucks. Not knowing the full nature of the issue I responded that it was probably a safe precaution in case a fire started. Landed safely with no issues. Postflight revealed that the alternator had seized and the burning smell was the melting of the alternator belt.




Synopsis: Pilot reported alternator failure that resulted in a precautionary landing.
Date: 201301
Local time of day: 0001-0600
Location: ZZZ.ARTCC, US
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Powerplant Lubrication System
Component problem: Malfunctioning; Failed
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Situational Awareness
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Flight Cancelled / Delayed; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On route we noticed the left engine oil temperature had risen into the caution range with the corresponding oil quantity indicating zero gallons at which time I started the timer for the 20 minute limitation and called for the appropriate Non-normal checklist. I initiated a phone patch with Commercial Radio to flight operations informing them of our situation and that I was planning to divert to the nearest suitable airport.  Having coordinated with Center I was cleared direct to the divert airport and started a descent. During this time the oil temperature had been in the caution range approximately 10 minutes but then reached the maximum temperature so I called for and we performed the Inflight Engine Shutdown checklist of the left engine.  I informed Center that I had shutdown an engine and was now declaring an emergency and we started our preparations for a single engine approach which was completed without incident.


Second narrative: Report contains no additional information.


Synopsis: A B757 engine oil was detected in the Caution Range with no oil quantity remaining so after waiting ten minutes when the oil temperature reached maximum; the QRH completed; the engine was shutdown; an emergency declared and the flight diverted to a nearby airport.
Date: 201502
Local time of day: 0601-1200
Location: CMA.Airport, CA
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Takeoff / Launch
Airspace: Class D CMA
ATC / advisory: Tower CMA
Reporter organization: Personal
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Communication Breakdown; Workload; Confusion; Distraction; Situational Awareness; Time Pressure
Anomaly: ATC Issue All Types
Detector: Person Flight Crew
When detected: In-flight; Taxi
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: When preparing for takeoff Camarillo Airport controllers expend very precious communications (radio) time (airwave availability) on unnecessary read backs and repeated read backs. This could cause; and has caused; in some instances; missed communications with aircraft that need to contact the control tower facility. This is especially critical when the Class D airspace is crowded with aircraft and aircraft operations. This could lead to confusion in the Class D airspace. I would like to suggest that all communications are kept 'Clear' and 'Terse' due to the crowded conditions at CMA airport. I have gotten complaints from other ATC facility personnel about operations at CMA and unnecessary radio communications. This seems to be a 'local' Camarillo issue and should be resolved with tower personnel immediately. I have personally experienced this issue with CMA ground and tower personnel in the past. I have; on occasion departed the Class D airspace while in the airport traffic pattern; because I have not been able to effectively break into the 'radio chatter' to make a position report. This is a safety issue and should not happen. Especially if a pilot is in the pattern.




Synopsis: Pilot reports of excessive chatter on CMA Tower frequencies.