elihoole/asrs-aviation-reports huggingface dataset:
Date: 202111
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Bonanza 33
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Propeller Pitch Change Mechanism
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Loss of power on take off; prop control released to low RPM. Planning off field landing. Requested priority handling with ZZZ Approach was able to regain some power by holding prop control in for high RPM and return to field. On the ground; inspection of the Vernier control for the prop pitch would not lock in place and slid out on its own to low RPM. Plunger button would not stay out to lock setting.




Synopsis: Bonanza 33 pilot reported engine power loss after take off and performed an air turn back to a precautionary landing.
Date: 202006
Local time of day: 1201-1800
Location: LAX.Airport, CA
Aircraft: Small Aircraft
Flight plan: IFR
Mission: Traffic Watch
Flight phase: Final Approach
Airspace: Class B LAX
ATC / advisory: TRACON SCT
Second aircraft: Commercial Fixed Wing
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
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
Result: Air Traffic Control Issued New Clearance
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Vectored Aircraft X for a Visual Approach to Runway 24R initially without a heading then later assigned a 230 heading to join final and issued traffic for south complex Runway 25L traffic Aircraft X had traffic in sight. Aircraft X passed through the final approach course getting close to the south complex traffic Aircraft Y; Aircraft Y was issued traffic but did not have them in sight. Aircraft X was given instructions to correct back to Runway 24R.Right now we are getting a lot of unfamiliar and less experienced pilots coming out flying at LAX due to slow downs during COVID and it's my responsibility to be extra diligent in ensuring these types of aircraft are doing what they need to [in order to] operate safely.




Synopsis: SCT TRACON Controller reported experiencing an airborne conflict between an air carrier and a GA aircraft.
Date: 201303
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: IMC
Light: Night
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Gear Pins
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: First Officer was PF; Captain was PM. After normal takeoff the PM moved the gear handle to the up position. The center gear primary and secondary lights remained red; the gear Non-Alert checklist was completed; and the PM contacted Flight Control and decided to continue at 260 knots or less.Aircraft was configured for landing early; and all gear indications were normal. A normal landing and roll-out was made. After shutdown; it was determined that the center gear pin had not been removed. An emergency was not declared.




Synopsis: MD-11 center gear failed to retract.
Date: 202001
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: PA-31 Navajo/Chieftan/Mojave/T1040
Flight plan: None
Flight phase: Landing
Airspace: Class E ZZZ
Reporter organization: Contracted Service
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Instrument
Human factors: Situational Awareness; Distraction
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Gear Up Landing; Ground Event / Encounter Ground Strike - Aircraft; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On approach to landing; the approach checklist was completed. The approach became high and a little fast. With the airspeed distraction; the landing checklist was not completed. In the flare to landing; a grinding noise was heard. A go around was accomplished. No gear warning horn was heard. A left traffic pattern was entered; the gear was positioned down; and the landing checklist was completed. A normal landing was accomplished and taxi to parking completed without incident. Upon shutdown; bent prop tips were noted. Looking back; an upwind approach would have provided more time to complete all of the checklists; and ensure the aircraft was configured to land.




Synopsis: A Pilot reported they became distracted recovering an unstable approach and did not complete the landing checklist resulting in a gear up landing attempt and prop strike.
Date: 201403
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: IMC
Weather elements / visibility: Fog
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Recip Eng
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Distraction; Workload; Time Pressure; Troubleshooting
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General Declared Emergency
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: At 5;000 feet in cruise above a fog layer with tops at 4;000 and bases at 1;800 on an IFR Flight Plan (TER) from ZZZ to ZZZ1; a loud; continual thumping noise began to come from the front of the aircraft. I declared an emergency with ATC and descended without clearance. ATC restricted my descent to 2;800 feet for the airport Class [D] airspace at my 12 O'clock. I needed to get visual to allow for more options in the event I was forced to make an off airport landing; but ATC refused lower. I descended through the ATC restricted level to 1;800 feet where I became visual with the airport and landed safely.I am under the impression that once I declared an emergency and it was recognized by ATC; that I could proceed in whatever manner necessary to survive the emergency with no restrictions. The Controller and the Supervisor both asserted that their rules superseded my emergency and that I was in violation of the altitude restriction.  The Controller also gave me a deviation vector for traffic which I refused to accept and he then vectored the opposing IFR traffic away from my flight path.  I am unable to find any regulation supporting the Controller or his Supervisor's actions.




Synopsis: Pilot declared emergency and ATC had issues with what pilot needed to do to get aircraft on the ground as soon as possible.
Date: 201812
Local time of day: 1801-2400
Location: LAX.Airport, CA
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Airspace: Class B LAX
ATC / advisory: Ground LAX
Reporter organization: Government
Reporter function: Ground
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Air Traffic Control
When detected: Taxi
Contributing factors: Aircraft; ATC Equipment / Nav Facility / Buildings; Airport
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Frequency bleed-over occurred again. Aircraft X called to push from on Ground 1 frequency. I was working Ground 2 on frequency and I heard Aircraft X on my frequency which has been a problem for some years now. I sent a previous report a couple of weeks ago. I just recommend investigating the equipment and determine why it happens with certain aircraft.




Synopsis: LAX Tower Controller reported one of the Ground Control frequencies receives bleed-over from another frequency from certain aircraft.
Date: 202005
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Descent
Airspace: Class D ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors; Staffing; Environment - Non Weather Related
Primary problem: Human Factors

Narrative: While in contact with ATC and cleared to descend at pilot's discretion I was told to contact ZZZ Tower. I was also told to avoid ZZZ1 airspace which I did. I was not told to avoid the ZZZ airspace. After numerous attempts to get through to ZZZ Tower contact was made. The Tower operator was extremely busy because the Tower was short on staff. This airport was doing a lot of training flights and was very busy. The Tower operator was handling both Ground Control and Tower operations. After finally making contact with the Tower; the Tower operator got upset because I entered his Class D airspace. I thought I was handed off by Approach Control to ZZZ Tower. I don't know if I was handed off by  Approach to ZZZ Tower; or if the Tower operator was to busy to realize what was happening.In the future I will make sure that before I enter controlled airspace I will be in contact with the person controlling that airspace and not depend on being handed off by another Controller. Even though I realize that I need to be more diligent about controlled airspace; I believe that because the Tower operator was so overworked is what really caused the problem. If the Tower operator was not doing Ground Control and Tower Control at the same time in an extremely busy facility radio contact could have been made much sooner and this would have never happened. I would suggest that in the future if the Tower is short on staff; the number of training operations be reduced so as to not overload the Tower operator.




Synopsis: Pilot reported an alleged airspace violation while being under flight following and handed off to a Tower by Approach Control.  Reportedly; Tower Controller was working numerous frequencies/positions and advised pilot that he had violated the Class Delta airspace.
Date: 201908
Local time of day: 1801-2400
Location: LVK.Airport, CA
Flight conditions: VMC
Weather elements / visibility: Sunset; 10
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class D LVK
ATC / advisory: Tower LVK
Second aircraft: Cirrus Aircraft Undifferentiated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: I was piloting as I entered the airport traffic pattern in a mid-field entry to right downwind Runway 25R at KLVK per ATC direction; I was also cleared to land #2 for Runway 25R behind a Cirrus on a 3 mile final. I acknowledged the clearance. As I approached abeam the numbers of the approach end of Runway 25R; I established my descent power settings; and flaps. I also glanced out my right passenger window and observed a white low wing aircraft on the ground (which I believed was a Cirrus; I was supposed to follow based on its higher approach speeds and being on final as I entered downwind). I continued into my descent; turned right base and looked towards the runway. There was severe glare from the setting sun on the horizon line; which made the airport difficult to see. I looked left; did not see any traffic and believed the Cirrus had landed and was the aircraft I observed prior. I turned final; confirmed I was on glide path with the PAPI and at approximately 700 ft AGL at 70 kts indicated; I was told by KLVK Tower to go-around. I complied immediately and notified Tower that I had a prior departed aircraft in sight. The Tower did not specify if I should off-set for the go-around; so I asked and was told to off-set to the north of the runway. I complied and followed directions to return through a normal pattern and approach; which concluded in a full-stop landing. I asked as to distances and spacing; which Tower was unable to provide. The Cirrus had not made any turns to avoid or radio calls to me or the Tower at the time this incident took place.




Synopsis: C172 pilot reported an NMAC in the traffic pattern; citing severe glare as a contributing factor.
Date: 201811
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant; Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate; General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Cabin crew collectively decided to allow a 'smart bag'; with a non-removable battery into the cabin. After reviewing company procedures; the cabin crew determined that the bag was not allowed. They notified the flight deck and we returned to the gate. The battery was removed and the flight continued without further incident. [Caused by] misinterpretation of FAA/company regulations/procedures. [Suggestions are] closer review of published material.




Synopsis: CRJ-700 Captain reported being notified during taxi of a smart bag mistakenly loaded in passenger cabin.
Date: 202007
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 15
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
ATC / advisory: TRACON ZZZ
Second aircraft: Other
Reporter organization: Personal
Reporter function: Pilot Flying; Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Conflict NMAC
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: After receiving a cancellation of an altitude restriction from ZZZ Approach we initiated a climb to 6;500 ft. to practice maneuvers. Another training aircraft had us in sight but also reported another aircraft in the same area that ZZZ Approach did not have on radar. We began searching for the unverified aircraft and then the aircraft passed roughly 100 ft. directly over us in a descent into ZZZ. We descended to avoid a collision. The unverified aircraft was a bright yellow crop duster based out of ZZZ.




Synopsis: C-172 Flight Instructor an NMAC event with a nonreporting crop duster during training flight.
Date: 201208
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: Turbulence; 40
Light: Daylight
Aircraft: Gulfstream G200 (IAI 1126 Galaxy)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Situational Awareness; Distraction; Training / Qualification
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft; Procedure; Weather
Primary problem: Weather

Narrative: In level flight at FL410 after being in cruise at altitude for approximately 1/2 hour; we experienced some moderate turbulence. Then we felt a buffet and the airspeed started decreasing. The autopilot started pitching the aircraft nose high to maintain altitude. I increased to max take-off power and disconnected the autopilot. We could not maintain altitude and the airspeed was decreasing so we requested descent to FL390. Upon reaching FL390 we continued to feel buffet and requested FL370. We continued the descent to FL370 and the turbulence cleared up. We continued the flight at FL370 for approximately 30 minutes in light turbulence. We requested FL390 for the rest of the flight and did not have any turbulence at FL390.




Synopsis: A G200 experienced an altitude loss in moderate turbulence at FL410 so after the autopilot pitched up and aircraft speed decreased to maintain FL410; the crew descended to FL370 to maintain stable flight.
Date: 201906
Local time of day: 1201-1800
Location: MIA.Airport, FL
Flight conditions: IMC
Weather elements / visibility: Thunderstorm; Turbulence
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B MIA
ATC / advisory: TRACON MIA
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: Taking off out of MIA on WINCO2. Passing 4;000 feet (climbing to 16000 feet); vectored to 340 heading. Saw two large cells (tops to FL550) between my position and BORLE intersection. Cleared on heading 310; direct BORLE when able. I told the controller I wanted a heading of 350 to pass to the north of both cells. I was told 'No;' aircraft are getting through the gap between the two cells. Skirted the first cell to the south; but the gap had closed. Immediately got severe turbulence from the cell on the right. Turbulence was severe (off and on) for 2-3 minutes. Aircraft also had two distinct short periods of uncontrolled flight. First Officer was commanding a right hand turn in both instances and the aircraft turned left 45 degrees. No over speed; no G exceedance; no altitude deviations; no aircraft limitations exceeded. No injuries. Flight attendants were told to remain seated. After 3 minutes; the aircraft exited the cell and was VFR.This event occurred because MIA Departure was unwilling to let me head 350 as requested to miss all storms. I understand that FLL airspace is just to the north of MIA and leaving me on a 350 heading would conflict with arrivals into FLL is a concern. Telling me that aircraft are getting through the gap only works until it doesn't. For our flight; it did not work. Once we turned to a heading of 310; we were committed. There just is not a lot of room between where we were and BORLE.If the crew does not want to try to shoot a gap; another solution should have been offered. Once on the heading toward the storms; the aircraft was committed! Turning right 270 degrees and skirting the storms to the south should have been offered. Luckily; no one was hurt and no aircraft damage was noted.




Synopsis: A319 Captain reported asking for a turn out of weather; ATC said no; flight went through area of severe turbulence.