elihoole/asrs-aviation-reports huggingface dataset:
Date: 202107
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: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: FBO
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Conflict NMAC; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: My student and I were practicing commercial pilot maneuvers in the South Practice Area of the ZZZ terminal area. We were .5 NM SE of [the lake] doing a steep spiral from 4;500 feet down. We made multiple radio calls and this was our second maneuver. After the first turn and a half; we were alerted to a traffic conflict on my iPad; which was supplied by a Sentry Mini ADS-B receiver. We looked for the traffic and spotted them on a collision course. We immediately terminated the maneuver and I took controls from the student to execute an emergency climb; as our paths were roughly perpendicular and I did not believe a turn would be enough to clear us. The other aircraft (C172) passed directly under us without making a control input or diverting course. We did some more maneuvers; also with thorough radio calls but had no further conflicts.




Synopsis: Flight Instructor reported taking evasive action due to a Near Mid Air Collision.
Date: 201807
Local time of day: 1201-1800
Location: BFI.Airport, WA
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 152
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Final Approach
Airspace: Class D BFI
ATC / advisory: Tower BFI
Second aircraft: Helicopter
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Situational Awareness
Anomaly: Conflict NMAC; Deviation - Speed All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: When on a traffic pattern visual approach to 32R at BFI; on the final approach leg a helicopter cut in front of [our] C152 at the same altitude. The helicopter was supposed to follow the C152 before landing on 'PAD6'. The flight instructor on the C152 decided to go around to avoid a mid-air collision with a helicopter; which caused the airspeed in the C152 to substantially drop at a low altitude.When the Tower was queried about the position of the helicopter; the Tower mentioned the helicopter should have followed the C152.




Synopsis: C152 instructor pilot reported a NMAC with a helicopter in the pattern at BFI airport.
Date: 201604
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Situational Awareness; Distraction; Communication Breakdown
Second reporter function: Pilot Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Landing Without Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Inflight Event / Encounter Unstabilized Approach
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: First Officer (FO) was Pilot Flying (PF) and cleared for a visual approach to Runway XYR; from base leg at 3;000 feet. FO chose to use LNAV and VNAV to backup approach. FO stayed too high because of improper programing; too distracted to take over visual; and fly aircraft. Repeated call outs to FO by Captain to descend but FO very unable to understand and think. Captain had to turn off LNAV & VNAV and instruct FO to follow ILS and Flight Director. In the confusion the Tower call for clearance to land was missed.This FO is very distracted by [personal difficulties and] is not 100% mentally dedicated to doing his duties.


Second narrative: On base to final; we received a visual clearance from Approach Control for Runway XYR. Upon landing I realized we were still with Approach Control. When we switched to Tower frequency; the Controller cleared us to taxi without further incident.


Synopsis: A B737 First Officer became highly distracted after mis-programming the FMS for a visual approach. The Captain commented First Officer's personal matters made him unable to perform his flying duties well.
Date: 201603
Local time of day: 1201-1800
Location: MMUN.Airport, FO
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
ATC / advisory: Tower MMUN
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Landing clearance issued by Cancun tower by about 1200 feet AGL. Normal approach VMC with good visibility but with some haze due to opaque sky cover and humidity. At 400 feet AGL; an unidentified aircraft holding short 12R announced 'there is a Cessna on the runway and you have an aircraft on short final'. At this we could now see the Cessna 172 stopped on the runway obscured by its blending in with runway colors. We initiated go around and notified tower. Control tower made no reference to aircraft on runway and later asked us reason for go around. Normal go around and circle back to 12R for normal landing. Tower seemed completely unaware of conflict. We believe we would have seen the Cessna prior to touchdown but at 400 feet we were in a position to land without aircraft in sight as yet due to its position 1000 feet down from runway takeoff end.




Synopsis: B737 Captain reported being cleared to land at MMUN by Tower. At 400 feet an unidentified voice reported a C172 on the runway; which the crew could now see; and a go-around was initiated. The Tower was unaware of why the crew went around.
Date: 201505
Local time of day: 0601-1200
Location: ZTL.ARTCC, GA
Flight conditions: IMC
Weather elements / visibility: Cloudy; 5
Light: Daylight
Aircraft: PC-12
Operator: Air Taxi
Operating under: Part 91
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class E ZTL
ATC / advisory: Center ZTL
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Flying
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Contributing factors: Procedure; Weather
Primary problem: Procedure

Narrative: Scheduled to operate an owner flight to A08. Preflight planning revealed no NOTAMs at A08 that would impact our arrival. Upon arrival in the Marion Alabama area Atlanta Center asked if we had weather and NOTAMs for A08. We asked the controller to review any new NOTAMs they had; the only NOTAMs reported were tower light outages; these were the NOTAMs we had reviewed prior to departure. The weather was 600 overcast with about 5 miles visibility. We were cleared to an initial fix and cleared for the GPS 16 approach. The approach went normally until breaking out around 500 feet. All of the runway markings were gone; a large yellow x was covering the threshold of the runway; and several construction vehicles were just adjacent to the runway at the midfield point. Also to note; position reports were made throughout the approach on CTAF. We executed a go around and held at the missed approach point. We informed ATC of the situation and they were unaware of any airport closures. After about 10 minutes ATC reached the airport manager who told them the airport was closed and that he had forgotten to produce a NOTAM to that effect. I explained the situation to our owners and they requested we divert to [another airport]. The diversion and GPS approach [to diversion airport] was uneventful. Following this event we informed Operations and Dispatch so that any of our other flights heading to Marion would be aware of the closure.




Synopsis: Upon breaking out at the completion of an instrument approach; crew of PC-12 noticed that the runway was closed with a large yellow X on the runway threshold. The entire airport had been closed for construction; but no NOTAM was issued. Crew diverted to an alternate airport.
Date: 201408
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: TRACON ZZZ
Aircraft component: Engine Air Pneumatic Ducting
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution; Flight Crew Overcame Equipment Problem; General Declared Emergency
Contributing factors: Weather; Aircraft
Primary problem: Ambiguous

Narrative: During climbout the Tail Compartment Temp high light illuminated. Performed the Memory items and followed the QRH procedure and the light extinguished. This was followed by the failure of the left pack. Declared an emergency and returned. Briefed the flight attendants; explained reason for our return to the passengers. Contacted Operations; and requested Operations contact Dispatch. [We] sent a message to Dispatch informing Dispatch of our situation. Requested ARFF observe the aircraft and follow us to the gate. Passengers deplaned upon arrival at gate.




Synopsis: MD83 flight crew experiences a tail compartment temp high during climbout and returns to the departure airport.
Date: 201409
Local time of day: 1201-1800
Location: PHX.Airport, AZ
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Cruise
Reporter organization: FBO
Reporter function: Instructor
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine

Narrative: While maneuvering with a student who is rated in the aircraft we got in close proximity to bravo airspace. Never got less than 500 FT below the shelf; but our transponder altitude was reading about 200 FT off of what the actual MSL value was.




Synopsis: A C172 instructor reports flying near but not in PHX Class B airspace. The aircraft transponder however was reading higher than the actual aircraft altitude.
Date: 201812
Local time of day: 0601-1200
Location: ORF.Tower, VA
Flight conditions: VMC
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class C ORF
ATC / advisory: TRACON ORF
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Aircraft; Airspace Structure
Primary problem: Aircraft

Narrative: I was receiving a position relief briefing while Air Carrier X was descending for an IFR approach. An untagged VFR target appeared and began climbing northwest bound; across [the aircraft's] final. A conflict alert activated and traffic was exchanged. This is a regular occurrence as the final approach is closely situated between two uncontrolled airports. The crossing altitude at the initial approach fix for the ILS approach is below the floor of Class C airspace. Without requiring communication with VFR aircraft in the area; these instances will continue.




Synopsis: A TRACON Controller reported an unindentified VFR target flew into confliction with an Air Carrier on final approach.
Date: 201507
Local time of day: 0601-1200
Location: GUC.Airport, CO
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Chancellor 414A / C414
Operator: Corporate
Operating under: Part 91
Flight plan: VFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: CTAF GUC
Second aircraft: Commercial Fixed Wing
Reporter organization: Corporate
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Commercial; Flight Crew Flight Instructor
Human factors: Communication Breakdown; Other / Unknown
Anomaly: Conflict Ground Conflict; Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Flew VFR and started announcing our intentions 20 miles to the east to land at GUC. On landing didn't see any other traffic. When I set the nose wheel down and looked down the runway here is a [commercial fixed wing aircraft] proceeding toward us on centerline on his takeoff roll. Both aircraft took action to the right of centerline and avoided each other. [Communicated] with Flight Crew; they said their radio was bad and they never heard us.




Synopsis: C414 pilot reports commencing CTAF procedures 20 NM out for landing at GUC with no response from other aircraft. After touchdown; another aircraft is noted taking off in the opposite direction. Each moves to the right and pass on the runway. The other aircraft's crew later reports they had a bad radio.
Date: 201811
Local time of day: 1201-1800
Location: MYNN.Airport, FO
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Landing
ATC / advisory: Tower MYNN
Second aircraft: Medium Transport
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: [We were] cleared to land runway 9 in Nassau. No hold short instructions of any kind were issued prior to touchdown. After touchdown and while braking to vacate the runway at taxiway H (the end of the runway); Tower Controller cleared Aircraft Y to depart runway 14; an intersecting runway with an obscured view of runway 9. [The] FO (PF) (First Officer; Pilot Flying) heard Aircraft Y's readback and queried the Captain. The crew transferred controls and Tower was asked if there was an aircraft taking off runway 14. Tower replied 'No.' The Captain was able to get the aircraft stopped before the intersection of the two runways. Aircraft Y was rotating and getting airborne prior to the intersection of the runways; but was cleared to takeoff during [our] landing roll. When asked again; Tower claimed to have issued instructions to [us] to hold short of runway 14. Neither the CA (Captain) nor FO heard; responded; or acknowledged any such radio call.It was a clear day; and there was minimal radio traffic on Tower frequency. Only the two aircraft involved in the incident were on the frequency at the time.




Synopsis: B737 First Officer reported a ground conflict during landing rollout when ATC cleared an aircraft to took off from an intersecting runway at MYNN.
Date: 201209
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: DC-10 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Cooling Fan; any cooling fan
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Troubleshooting; Training / Qualification; Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Aircraft In Service At Gate
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: [I received] a gate call [on a DC-10] with an air system fail alert on pre-flight air system test. After getting the MEL to do the logbook entry; the circuit breaker would not reset. I collared [the circuit breaker] to prevent anyone else from trying to reset it. After looking into the System Schematic Manual Chapter 21-26-0; I realized that the breaker just controlled the Number 3 fan. I was trying to prevent any further aircraft problems. It also had no history for that discrepancy. I figured the system was inoperative and [that I was] collaring a breaker that would not reset; [so] I just collared it. I collared the breaker just to prevent anyone else from trying to reset. There was no question about safety of flight. I did the research to make sure the breaker did not affect any other components. I should have contacted Maintenance Control. I will contact Maintenance Control and make sure I go by the MEL to the letter and will not deviate. [I will] collect all information and with Maintenance Control; make a decision. Use my resources. I have seen where they put out maintenance alert about this type of problem in the last couple of day. MEL 21-26-05; is a good [reference] to be used if you have a bad cooling fan that fails an operational check; [but] not if the circuit breaker pops.




Synopsis: The Maintenance Technician attempted to comply with the MEL for an avionics cooling fan fault; but discovered that the circuit breaker would not reset. He utilized the MEL and collared the circuit breaker thinking that is was only affecting that fan. By doing so; he did not comply with the approved MEL procedure.
Date: 202109
Local time of day: 1801-2400
Location: ZJX.ARTCC, FL
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class A ZJX
ATC / advisory: Center ZJX
Reporter organization: Air Carrier
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Distraction; Situational Awareness; Confusion; Communication Breakdown
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Airspace Structure; Chart Or Publication; Procedure
Primary problem: Chart Or Publication

Narrative: I was working the shift when there was a reentry Dragon rocket. The packet with the information only had the landing zone and the monitoring aircraft. The problem was there was no information on the reentry flight path so it caught me by surprise when it was coming in over the top of my traffic. All of the airplanes started asking what it was and I didn't know which direction to call traffic for any of them or give them an option of the area to miss if they were uncomfortable with the situation.My recommendation is more information passed along. I had multiple airplanes close to the flight path and I had no way of helping them if they needed vectors because they were uncomfortable.




Synopsis: Center Controller at ZJX reported they were not given sufficient information about a rocket reentry and could not provide traffic information or vectors for separation to aircraft in their sector.
Date: 201903
Local time of day: 1201-1800
Location: FCI.Airport, VA
Flight conditions: Mixed
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Initial Approach
Airspace: Class E PCT
ATC / advisory: TRACON PCT
Reporter organization: Personal
Reporter function: Single Pilot; Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was being vectored onto the final approach course for the RNAV/GPS-15 approach into FCI. Was at assigned altitude 2600 feet. Received clearance '[tail number] turn right heading 160; maintain 2000 until established; cleared for the RNAV runway 15 straight in approach Richmond Executive'. I read back '120 maintain 2000 until established; cleared for the RNAV 15 Richmond Executive [tail number]'I intercepted the final approach course outside of SECOV (the FAF) and began my descent down to 2000 in VMC. Shortly thereafter; I received a 'low altitude' warning on my FMS and realized that I had descended below the 2200-foot minimum altitude for the segment between DOCEV and SECOV. At that point; I was VMC; cancelled IFR; and continued with a normal straight-in approach for landing.The particular controller speaks very quickly and it is sometimes hard to hear her above the background static. I listened back to the recording several times on liveatc.net and after slowing the recording down to 2/3 or normal speed; I can now hear that she said; 'Maintain two-thousand-six-hundred until established'. I read back 'maintain two-thousand until established' and was not corrected. In hindsight; I should have not descended below the segment's minimum altitude regardless and simply waited for the LPV vertical guidance needle to center while at 2600 feet.




Synopsis: GA pilot reported a communication breakdown with ATC led to an excursion from altitude while on approach to  Richmond Executive Airport.