elihoole/asrs-aviation-reports huggingface dataset:
Date: 202010
Local time of day: 0601-1200
Location: MSY.TRACON, LA
Flight conditions: VMC
Weather elements / visibility: Cloudy
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class D NEW
ATC / advisory: TRACON MSY
Reporter organization: Personal
Reporter function: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Distraction
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Procedure
Primary problem: Procedure

Narrative: Upon arrival in NEW airspace. ATC cleared [us] for approach via SAFES IAF to RNAV runway 36L. Clearance was then modified and was told to stay at 3;000 ft. until further advised for departing traffic. Aircraft flew past initial approach descent point. FMS dropped vertical navigation guidance at that point. A manual descent was initiated just prior to that. I hurriedly reloaded the FMS to re-establish vertical guidance. While reloading; I received a low altitude alert from ATC with my call sign. I appeared to be in the vertical path of the approach just inside TOYBO at 2;400 ft. I had the runway insight and asked for and was cleared for visual approach.I am unsure if descent rate or altitude tripped the low altitude warning issued by ATC as I appeared to be in parameters while trying to re-establish the approach in the aircraft FMS.Flight continued to runway on glide path with nothing unusual other than the low altitude warning from ATC near TOYBO intersection.




Synopsis: Pilot reported a Low Altitude alert on approach to NEW airport.
Date: 201708
Local time of day: 0601-1200
Location: MIA.Airport, FL
Flight conditions: VMC
Light: Daylight
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Initial Approach
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)
Human factors: Fatigue; Situational Awareness
Anomaly: 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 Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On arrival into MIA landing 26R we were told to expect the RNAV 26R. We mistakenly edited the HILEY6 arrival with the instructions on the procedure that were listed in the Lost Comm Box for landing west operations. After waypoint HILEY we proceeded to HOXIL. After we turned to HOXIL; Approach Control asked us if he had given us a heading. We responded that he had not but we were following the landing west procedure. We said that we were incorrect and that crews often make this same mistake. He told us not to worry about it and cleared us direct to NAYIB for the RNAV 26R. We landed; taxied; and shutdown uneventfully.Fatigue was a big factor for us. This was the second leg of [a day that included] holding and heavy storms. Many planes were delayed inbound and or required to divert due to low fuel. The presentation of the arrival chart also added to our misinterpretation; as well as other prior crews apparently. This chart was especially confusing and counter intuitive during landing west ops in MIA. More careful review of the arrival and more effective awareness of our state of fatigue.




Synopsis: A300 Captain reported a track deviation on arrival into MIA. Chart design and fatigue were cited as contributing.
Date: 202008
Local time of day: 1201-1800
Location: SFB.Tower, FL
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: FBO
Operating under: Part 91
Flight plan: IFR
Mission: Training
Flight phase: Initial Approach
Second aircraft: UAV - Unpiloted Aerial Vehicle
Reporter organization: FBO
Reporter function: Instructor; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While on approach for ILS 09R at SFB; Instructor noticed a small black dot at 11 o'clock. We were about half a mile from the final approach fix at 1600 ft.; flying at 110 kts; when Instructor noticed the object. As we grew closer to the object; the sun shined a reflection on the object and that is when Instructor discovered that it was not in-fact a bird; but a drone; as it did not have wings and for the fact that the sun does not shine like that on birds. Instructor kept visual contact as it went from 11 o'clock and then slowly past our left wing at the same altitude; seemingly hovering at its same position. Due to the small size of the object; it was difficult to judge how far away it was; Instructor roughly estimates about 100 ft. Instructor roughly estimates the object size was about 1ftx1ft. No deviation was required. Instructor reported to ATC of the activity; who then relayed the information to other inbound traffic. Flight continued normally.Suggestions: As there were no NOTAMs or information from ATC about drone activity; this particular incident seems to have been conducted against FAA regulations for UAS. Scanning for birds and UAS; in addition to other aircraft; should be constant when able.




Synopsis: GA Instructor reported an NMAC event during approach to SFB with a Drone at an altitude of 1600 feet.
Date: 201905
Local time of day: 0601-1200
Light: Daylight
Aircraft: Extra 200/300 Series
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Aircraft component: Powerplant Fuel System
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Other / Unknown; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Fuel Issue
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Trying to photograph skydivers by request and could not get the plane to slow to the speed of the jump plane without an extreme AOA. The problem was the extreme AOA was starving fuel when the tanks were below 50%. On one occasion the engine failed and I had to dive to regain power and then climb into almost a loop to then slow the plane and to regain altitude. The plane can handle the G loads as it was designed to do so; however; this portion of the flight was over the small urban area east of the field.




Synopsis: Pilot of Extra 300 reported difficulty completing a photographic mission.
Date: 201703
Local time of day: 0601-1200
Location: ZLA.ARTCC, CA
Light: Daylight
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Confusion; Human-Machine Interface; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Chart Or Publication; Company Policy; Procedure
Primary problem: Chart Or Publication

Narrative: OAPM (Optimization of Airspace and Procedures in the Metroplex) aircraft did not have updated stars for destination airport. Did not have either DSNEE1 or DOOBY1 STARs. Ensure airlines are getting updated information.




Synopsis: ZLA Center Controller reported an aircraft did not have the updated OAPM Arrival procedures for their destination.
Date: 201911
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Ignition System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Workload
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
When detected: Aircraft In Service At Gate
Result: General Maintenance Action; General Flight Cancelled / Delayed
Contributing factors: Aircraft; Human Factors; MEL; Procedure
Primary problem: Human Factors

Narrative: Apparently Maintenance Control by their mistake while doing the Dispatch Release and sending it out Maintenance Control put in both MELS 74-XX-XX-XX ; Only one can be MELed but not both.During the time I was working on the release for this flight I believe there was only one MEL 74-XX-XX-XX then I clicked on the RLSE button again and somehow Maintenance Control put in both MEL for the RH and LH Ignition SYS A. I failed to notice this and the release was sent.




Synopsis: Dispatcher reported aircraft was released with both ignition system A and system B on MEL in error.
Date: 201901
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZ
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; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Flight Attendants reported smoke coming through the forward galley floor behind carts. [Advised ATC] and diverted to ZZZ for maintenance. AML entry made.




Synopsis: A321 First Officer reported receiving notification from Flight Attendants that smoke was emanating from forward galley behind carts. Flight crew diverted to an alternate airport.
Date: 201908
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Dawn
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Aircraft component: Exhaust Manifold
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Student
Human factors: Confusion; Distraction; Time Pressure; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: This flight was to be my second solo cross country for my ASEL PPL. My instructor had signed off on everything in my logbook and had the current briefing from both airfields. I was about 50 nm into my flight; switching on the 2nd COM to listen to the ASOS at ZZZ; when I heard a pop in the engine and had a significant RPM drop. I scanned all my instruments and didn't notice anything critical other than a loss of RPM. I decided not to add power as the engine was running very rough and I didn't want to exacerbate any problems. I scanned my EFB for the nearest airport and saw that I was about 23 nm from ZZZ. I trimmed for best glide speed and started trying to troubleshoot the problem. I thought maybe I had fouled the plugs; or had a mag fail. I cycled the mags and went back to both with no improvement. I then pulled in the carb heat to check for carb ice; but had no improvement. The engine was still running but I was losing RPM quickly. I immediately started for a field to set the plane down in and squawked 7700. I looked at my emergency checklist one more time; and decided to add power. I enriched the mixture and pushed in the throttle to try and re-gain some of my lost altitude. The engine did restore to the point of being able to maintain 3;000 feet. I then re-squawked 1200. I quickly looked at my EFB and saw that ZZZ1 was closer by about 5 nm and I diverted there. I called the CTAF at ZZZ1 and had a short approach landing. Once on the ground; I removed the cowling and discovered that an exhaust stack had split into the muffler. I contacted my local A&P and the parts are now ordered and will be installed shortly.




Synopsis: Cessna 172 student pilot reported the failure of the engine exhaust stack resulting in reduced engine performance; and a subsequent diversion to the nearest suitable airport.
Date: 201204
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Light: Daylight
Aircraft: B767-200
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: Flap/Slat Indication
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Troubleshooting
Second reporter function: Captain
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft; Company Policy
Primary problem: Aircraft

Narrative: After level off at FL340; flap indicator flickered and clicking sound was heard over head. We called Dispatch and Maintenance and we were told it was OK to continue. After passing over a major airport; the LE SLAT ASYM EICAS and LE FLAP Caution light illuminated and stayed on. At that time; there were no unusual handling characteristics; buffeting or rolling. Nearing our destination we notified ATC that we were declaring an emergency and needed to get lower and slower to complete the Emergency checklist. Completed QRH for LE Slat ASYM and landed 25R.


Second narrative: [Narrative #2 contained no additional information.]


Synopsis: A B767-200 EICAS alerted LE SLAT ASYM and the LE FLAP Caution light illuminated in cruise flight with no unusual flight characteristics so an emergency was declared; the QRH followed and the flight continued to its planned destination. Previously a clicking sound from overhead was heard and the flap indicator flickered.
Date: 202105
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B737-400
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb; Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Elevator Trim System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Yesterday we were flying ZZZ1-ZZZ. I was Pilot Flying. The flight was smooth and VFR going into ZZZ. ZZZ was landing Runway XX. The aircraft was downwind and I was at speed 230 and asked for flaps 1; speed 190. Once the flaps started coming out we noticed a light vibration which was consistent. Like driving down a bumpy road. The vibration continued until the gear came out and we slowed to 150. The rest of the landing I did not notice the vibration continue on landing. We landed; exited the runway and parked. Our Maintenance person went outside to do an inspection of the airplane and see if he could find the cause of vibration. The pilot monitoring and me also went out to see if we noticed anything unusual. Extended the flaps and the spoilers checking everything. Maintenance did not see an issue. The second flight going from ZZZ-ZZZ2 I was pilot monitoring. After lift off we noticed the same vibration very quickly. We retracted the gear and flaps on schedule. Then the PF (Pilot Flying) leveled off at 3;000 feet. We still had the same vibration and decided to return to ZZZ. Not exceeding 210 knots. The weather was still VFR and we landed Runway XX. We did not [request priority with ATC]. Once parked; our Maintenance person started a full inspection of the airplane. Into the inspection the elevator trim on the left of the tail was different than on the right. The Captain went into the cockpit and moved the flight controls up and down and the left trim tab was not moving the same as the right side. Maintenance personnel went up and inspected the trim tab on the left and found the control rod was not connected and it moved freely. Making a strange sound. Shortly after this we were told to head to the hotel so Maintenance could work on the issue. The aircraft recently sustained substantial damage in ZZZ3. The aircraft tail was damaged. I believe the two are connected. We came back and landed in ZZZ; very quick flight.




Synopsis: Air carrier First Officer reported flight control vibration in flight and did an air turn back.
Date: 201601
Local time of day: 1201-1800
Location: N90.TRACON, NY
Aircraft: Medium Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E N90
ATC / advisory: TRACON N90
Second aircraft: Large Transport
Reporter organization: Government
Reporter function: Approach; Departure
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; 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 Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic
Contributing factors: Airspace Structure; Chart Or Publication; Human Factors; Procedure
Primary problem: Human Factors

Narrative: JFK was landing Runway 4R and departing Runway 4L. On this flow arrivals from the northwest arrive north of JFK and are vectored to the east and south of the airport for their arrival. 4L departures depart and turn to a 100 degree heading to avoid LGA airport operations. Aircraft X departed and according to the summary was climbed to 7;000 and on a 100 degree heading. Aircraft Y was on a 120 degree heading north of JFK descending to 8;000. Aircraft X was instructed by me to turn right to a 180 degree heading and aircraft Y was instructed by the arrival controller to turn to a 220 degree heading. Aircraft X was instructed to climb to 12;000 and turned to a heading of 220 degrees. Aircraft Y was advised to maintain 9;000 and turn left heading 180 degrees. Separation was lost when aircraft X climbed through 9;000.I believe the arrival controller was busy and on our normal procedures he should have flown over JFK and turned to a 180 degree heading and descended to 8;000; but because of volume he took aircraft Y out east for more room as he was busy. I believed he would continue descending southeast bound and I would climb south of his arrival. This is not our normal procedure. So I believe we coordinated something and we both believed we were on the same page; but as we now can see the coordination and communication was not complete. Or not perfectly understood by both controllers.Better communication and coordination. We all must know the exact plan. Partial or misunderstood coordination is no coordination. We all must be on the same page especially when we are deviating off normal procedures. If we are doing something outside normal procedures we must [be] absolutely [certain] we know what each other are doing with our traffic.




Synopsis: Two N90 TRACON Controllers vectored descending/climbing aircraft for separation. One Controller believed the other Controller's aircraft would continue on a different heading than it did. The aircraft passed with less than required separation.
Date: 202105
Local time of day: 1801-2400
Location: LWC.Airport, KS
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: Cruise
Airspace: Class E ZKC
ATC / advisory: Center ZKC
Second aircraft: Small Aircraft
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Communication Breakdown
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was returning from LWC to ZZZ at 2;500 MSL approximately 9 miles NW of LWC heading NW.  I Encountered another small aircraft maneuvering at my 8 o'clock.  Aircraft went underneath and then turned and climbed toward me at my 5 o'clock.  It appeared the aircraft was performing commercial maneuvers (chandelle?) in a possible training flight. Best option was to add power versus trying to make evasive turn north or south since I wasn't sure if the other aircraft saw me.  Landed at ZZZ without incident.




Synopsis: GA pilot reported an NMAC while in cruise flight with another small aircraft that was executing practice maneuvers.