Recent national uptick in 'close call' runway incursions sparks local conversation

A Cessna C150 landed on Runway 23 without authorization at Tri-Cities Airport on a calm, fair-skies afternoon in December 2004.The pilot did not acknowledge light gun signals, which are used by air traffic controllers to direct aircraft if radio communications are out on the ground, if the aircraft has no radio, or if communication can't be established.The two-seat Cessna, used primarily for training and personal use, exited the runway, taxied back and departed — again without authorization, according to Federal Aviation Administration records.What is a runway incursion?Any occurrence at an aerodrome involving the incorrect presence of an aircraft, vehicle or person on the protected area of a surface designated for the landing and take off of aircraft.What is a surface incident?A surface incident is an unauthorized or unapproved movement within the designated movement area (excluding runway incursions) or an occurrence in that same area associated with the operation of an aircraft that affects or could affect the safety of flight.There are four categories of runway incursions:Category A is a serious incident in which a collision was narrowly avoided.Category B is an incident in which separation decreases and there is a significant potential for collision, which may result in a time critical corrective/evasive response to avoid a collision. Category C is an incident characterized by ample time and/or distance to avoid a collision. Category D is an incident that meets the definition of runway incursion such as incorrect presence of a single vehicle/person/aircraft on the protected area of a surface designated for the landing and take-off of aircraft but with no immediate safety consequencesIncursions at Tri-Cities AirportAt Tri-Cities Airport, only 20 incursions have been reported in the past 20 years. The three most common types of errors are pilot deviations, operation errors and vehicle or pedestrian deviations.Incursions are categorized by severity, assigned a letter A through D, with Category A being the most severe. Of the reported incursions, Tri-Cities has only dealt with Category C and Category D level of severity incursions.Depending on the incursion and its severity, the airport handles each situation immediately but differently."Any time there is an incursion of any type, the air traffic control people make a record of that, and they report it up to their safety and security offices," Cossey said. "Those safety offices will assign an investigation to it."Source: Federal Aviation AdmininistrationThe plane landed again, and this time was met by airport security, the records state. The pilot, making his second solo cross-country flight, believed he was at Greeneville Municipal Airport and had been communicating on that frequency.At Tri-Cities Airport, 20 runway incursions have been reported in the past 20 years, according to FAA records examined by the Kingsport Times News.Of those, 10 involved an aircraft taking off or landing without authorization, most recently on Aug. 16, 2022, when a propeller-driven plane landed on Runway 23 without traffic control clearance. Meantime, a business jet was on the runway getting ready to depart.Six other incursions involved vehicles, including a fuel truck, the records state.WHAT ARE INCURSIONS?An important part of air traffic control is giving directions and orders to pilots and other staff members to keep everything in order. If an order is disobeyed or not heard, that is considered a runway incursion."A runway incursion occurs when an aircraft, vehicle, or person enters a runway without authorization and poses a potential collision risk to other aircraft on the same runway," said Hassan Shahidi, president & CEO of the Flight Safety Foundation."In the best-case scenario, a runway incursion may result in a delay or inconvenience for passengers, while in the worst-case scenario, it could lead to a collision, which hasn't occurred. The majority of runway incursions in the U.S. have not been serious ones, but nevertheless are undesirable and must be eliminated."There has been an increased concern about runway safety after the FAA called a special summit last month following recent close-call incidents. The summit took place in McClean, Virginia, making it the first one of its kind since 2009."When I called this gathering a few weeks ago, it was because we had seen an uptick in incidents across the aviation system," said acting FAA Administrator Billy Nolen. "In the intervening time, we've experienced additional incidents, including events on runways, terminal area ramps — and even unruly passenger incidents that continue to defy logic."Chattanooga — 28Knoxville — 83Memphis — 100Nashville — 105Tri-Cities — 20SOURCE: Federal Aviation Administration; since 2003INCURSIONS AT TRI-CITIES AIRPORTThe three most common types of errors are pilot deviations, operational errors and vehicle or pedestrian deviations.Incursions are categorized by severity, assigned a letter A-D, with Category A being the most severe. Of the reported incidents, Tri-Cities has dealt only with Category C and Category D incursions."The vast majority of runway incursions are not serious occurrences," explained Tammy Jones, an FAA spokesperson, via email. "However, reducing the risk of them occurring remains one of the FAA's highest safety priorities and is a shared responsibility that encompasses pilots, air traffic controllers and airport vehicle drivers."Depending on the incursion and its severity, the airport handles each situation immediately but differently."Any time there is an incursion of any type, the air traffic control people make a record of that, and they report it up to their safety and security offices," Tri-Cities Airport Executive Director Gene Cossey said. "Those safety offices will assign an investigation to it."According to the FAA, airports with an FAA-controlled tower are required to hold at least one Runway Safety Action Team meeting each year. These meetings include air traffic controllers, pilots and vehicle drivers to ensure everyone is on the same page."The direct dialogue at these meetings is key to identifying measures to prevent runway incursions, and pilots who attend them become more aware of the incursion risks," according to Jones.TYPES OF INCURSIONSPilot deviations are the most common and will be reported to the Flight Standards District Office. Vehicle or pedestrian deviations are reported to the airport safety office and are independently investigated by the airport as soon as they are reported. Cossey said investigators address the five W's and one H: who, what, when, where, why and how, and try to make sure the incident won't happen again.Cossey mentioned the airport has many proactive policies in place through training and security controls that help limit the number of incursions. All employees are required to participate in annual training to go over FAA rules and regulations. At the yearly Local Runway Action Safety Team meetings, the team reviews significant incursions that occurred over the past year and look ahead to other potential issues like runway construction.Since Cossey started his job at Tri-Cities Airport in January 2019, only five incursions have taken place there. He attributed this number partly to the size of the airport itself."We're a very busy airport for our size, but when you compare an airport our size to say a Nashville size, or Atlanta size or [John F. Kennedy International Airport] size, obviously we're going to have less incidents because we have less operations," Cossey said."It's a rule of numbers where we have less operations going on, we're going to have less incidents going on."The Federal Aviation Administration recorded the following runway incursions at Tri-Cities Airport since 2003. These summaries are verbatim from the FAA:Jan. 4, 2004 — An unidentified Ford van (white) entered Taxiway Alpha from the east of the terminal building without authorization and passed a taxiing C150. No other conflicts reported.Nov. 16, 2004 — ATCT observed a Bell B06 (helicopter) crossing Runway 23 without authorization then enter Taxiway Charlie. No conflicts reported.Dec. 16, 2004 — A Cessna C150 entered Class D airspace and landed Runway 23 without authorization or acknowledging light gun signals. The C150 exited the runway and taxied back and departed Runway 23, again without authorization. Pilot entered right closed traffic and landed again without authorization or communications with ATCT. No conflicts reported. Airport security met the aircraft on the taxiway. Pilot thought he was at GCY, a nearby airport, and was making traffic pattern advisory reports on GCY's unicom freq. Pilot was conducting his second solo cross country training flight.April 14, 2009 — A Piper PA28A crossed Runway 23 hold short line at Taxiway Alpha (approach end) without clearance. A Beech BE20 on 1.5 mile final Runway 23 at the time was told to expect a go around. The PA28A attempted to turn around and clear the hold lines but was unable to do so and the BE20 was issued a go around at one half (.50) mile final to avoid loss of separation.May 23, 2013 — SR20 landed Runway 5 and was instructed to exit the runway at Taxiway Charlie. C82R called ready for departure from the approach end of Runway 5. Anticipating the SR20's exit, ATC issued a takeoff clearance. SR20 missed the turn at Taxiway Charlie. ATC had to cancel the takeoff clearance of the C82R who had begun departure roll. The SR20 was instructed to make a 180 and proceed to Taxiway Charlie and exit. The closest proximity between the aircraft was estimated to be 5,000 feet. C82R exited at Taxiway Romeo and taxied back to Runway 5.March 5, 2014 — Ambulances were called to the airport due to injuries to airport personnel working in the vicinity of the mid-field runway intersections. The first ambulance was escorted to the scene, but a second ambulance much further behind was unescorted and crossed the mid-field intersection of the two runways (5-23 and 9-27) without clearance or escort. COL3 was on an instrument approach to Runway 23. COL3 had leveled off a 2000 msl on a 1.5-mile final and eventually issued a go-around on a half-mile final, turning south.June 12, 2014 — Fuel truck was observed entering Runway 27 from a taxilane near the approach end. Vehicle did not communicate with ATC. Vehicle drove west on Runway 27 and exited at Taxiway Romeo. It was at that point that ATC was able to establish communication with the vehicle. No conflicts.October 19, 2015 — ATCT cleared A/C 1/C172 to taxi Runway 23 via Taxiway Alpha. C172 responded, via alpha, thank you, no callsign utilized. A/C 2/CRJ2 on final Runway 23 was cleared to land. ATCT observed C172 cross hold short line for Runway 23 at Taxiway Alpha. ATCT instructed C172 to hold position. ATCT advised CRJ2 of aircraft across hold line, but short of runway and asked intentions. CRJ2 advised intentions to continue. CRJ2 landed Runway 23, closest proximity approximately 150 feet.May 24, 2016 — A/C 1, C172, landed Runway 23 and veered off the runway then initiated a go around. No other aircraft involved.April 30, 2017 — Veh 1, fuel truck, contacted ground control for a clearance from the ramp on the east side of the airport over to the FBO ramp on the west side of the airport. When veh 1 called for the clearance, it was already on Runway 27 without clearance. Runway 27 was an inactive, no conflicts.December 4, 2017 — Veh 1, fuel truck, crossed Rwy 23 without authorization or clearance. No conflicts. Veh 1, fuel truck requested to proceed from the ASG hangar back to the north ramp. LC instructed the vehicle to proceed via Runway 27 and Romeo hold short of Runway 23 at Taxiway Romeo. The vehicle read back Runway 27 and then something unreadable, then hold short of Runway 23. The vehicle then proceeded across Runway 23 at Romeo without a clearance. The vehicle was informed that they were not supposed to cross the runway without a clearance and the FBO operator was called. No loss of separation.January 10, 2018 — A/C 1, (military) ch-47, entered Rwy 23 without authorization or clearance. No conflicts. GC issued the CH-47 taxi instructions to Runway 23. CH-47 reached the hold short line and stated for clarification that they wanted to take Taxiway A to the numbers for Runway 23 departure. GC acknowledged and instructed the CH-47 to contact local control (LC). CH-47 then taxied unauthorized on to Runway 23 without calling LC. LC called to CH-47 and the pilot stated GC cleared him to depart. LC issued departure instructions and departed the CH47. No loss of separation.September 27, 2018 — A/C 1 (h60) was issued taxi instructions to Rwy 23 via WY Alpha, with correct read-back. On arriving at the approach end of Rwy 23, A/C 1 crossed the hold-short line without authorization from ATC. No other aircraft involved. Validated no loss of separation.November 3, 2018 — Pd ri no conflict: A/C 1 (PT17) received a VFR clearance and taxi instructions to Rwy 23. upon reaching the runway, A/C 1 departed without clearance from ATC. No loss of separation.September 8, 2019 — Aircraft 1 (BE35) entered Runway (RY) 23 at the approach end without ATC authorization, no conflict. ATC instructed aircraft 1 to taxi to RY 23. Aircraft 1 read back taxi instructions correctly, but did not hold short of the RY. Once aircraft 1 taxied unto the RY, ATC cleared the aircraft for take-off. No other aircraft were affected.October 27, 2019 — Aircraft 1 (PA22) departed Runway (RY) 23 from the approach end without ATC authorization, no conflict. The tower controller taxied aircraft 1 to RY 23 via Taxiway (TWY) A. Once holding short of RY 23, aircraft 1 switched to the radar departure controller frequency and advised ready for departure. the radar controller instructed aircraft 1 to go back to tower frequency, but aircraft 1 remained on the departure controller frequency. Aircraft 1 entered RY 23 and departed. The tower controller observed aircraft 1 begin departure roll and issued aircraft 1 a take-off clearance with no response from aircraft 1. No other traffic involved. No loss of separation occurred.September 12, 2021 — Vehicle crossed Runway 23 without ATC authorization. Vehicle requested to proceed from the maintenance hanger and cross Taxiway Y into the field. All positions in the tower were combined. ATC issued TRACOR21 change to his local control frequency. ATC instructed vehicle to "cross Taxiway Y into the field and hold short of RWY 23 at all times." The driver incorrectly read back "Cross 23 at Y, hold short of 23 at all times." ATC did not correct the incorrect read back. No other traffic was involved.December 13, 2021 — Aircraft 1 departed Runway 23 without ATC authorization. Aircraft 1/SR20 was issued taxi instructions to Rwy 23. LC noticed that aircraft 1 had taxied past the hold short line on TWY A. As aircraft 1 took the runway without a clearance, the local controller asked if they were ready for departure. Aircraft 1 responded "we are rolling now" and departed Runway 23. No other traffic was involved.August 16, 2022 — Aircraft 1 landed Runway 23 without ATC authorization. Aircraft 1/M20p inbound VFR full stop to Runway 23 was switched to LC on approximately a 1-mile final. The pilot's read-back was correct. LC attempted to establish communication with the pilot with no response. Aircraft 1 landed on Runway 23 without ATC clearance. Aircraft 2/c68a was 3000 feet down Runway 23 on departure when aircraft 1 crossed the threshold.