|
|
|
|
|
|
|
 |
||||||||||
|
A year-to-date comparison of incursions between this year and last year is provided. FAA categorizes incidents to assess severity and to determine the best intervention strategies. ASF gratefully acknowledges the support of the FAA Office of Runway Safety in providing this information. Test your knowledge with ASF's Runway Safety Program, an online training course designed to teach pilots about runway incursion avoidance.
DATE: : April 4, 2004 NARRATIVE: : Aero Commander 114 (AC114), was cleared to land Runway 27R. Shortly thereafter, the AC114 was instructed to change its landing runway to Runway 27L for departing traffic on Runway 27R. The pilot of the AC114 acknowledged the landing clearance change for Runway 27L. Local Control instructed a Cessna C525 (C525), to taxi into position and hold Runway 27R. As the C525 was taxing into position, the pilot observed the AC114 over fly him. The AC114 over flew the C525 and landed on Runway 27R without clearance. Vertical separation was reported as 100 feet. ASF COMMENTS: : The AC114 pilot not only heard the change in clearance, he acknowledged it. It is the pilot's responsibility to understand and comply with a landing clearance, and it is especially important at airports with parallel runway operations. If at any time you are not sure about a clearance, ASK!
DATE: : September 23, 2003 NARRATIVE: : Local Control (LC) cleared the PA28R to land Runway 12R. One minute later LC cleared the PA46T for take-off Runway 7. The PA28R and the PA46T collided at the intersection of Runway 12R and 7. ASF COMMENTS: : Both pilots were very fortunate to walk away from this collision. Although the accident investigation is still in its early stages, preliminary investigation indicates it may have been caused by an operational error on the part of ATC. Regardless of who is at fault, pilots should look for aircraft on other runways prior to takeoff and landing. For more information about this accident, the preliminary report can be found in ASF's online online database by entering the NTSB accident number LAX03FA298A.
DATE:: February 20, 2003 NARRATIVE: : Local Control (LC) was told during position relief that a Cessna 402 (C402) was taxied into position and hold on Runway 32 approach end (displaced threshold). LC then cleared a Cessna 182 (C182) to land Runway 32. The C182 over flew the C402 between 200-300 feet vertical and landed 3000 feet down the runway. ASF COMMENTS: : Even when operating as directed by ATC, as both airplanes were in this case, it is still up to the pilot to visually verify that the runway is indeed clear and safe for landing.
DATE: : December 27, 2002 NARRATIVE: Cessna C172, after landing Runway 5, was instructed to turn left onto Taxiway F and contact Ground Control for taxi back to Runway 5. No hold short instructions were issued. The C172 turned left onto Taxiway F, then turned left onto Taxiway A and crossed Runway 30 in front of a Mooney MO20, on landing roll, but had not established 2-way ground communication. The MO20 pilot observed the C172 enter the runway, and moved to the left side of the runway, at taxi speed, to avoid a collision. Closest proximity reported was less than 50 feet. ASF COMMENTS: According to the AIM Chapter 4-3-20, the following procedures should be followed after landing and reaching taxi speed.
DATE: November 2, 2002 NARRATIVE: Piper PA28 (PA28-1), landed Runway 22 and had turned left onto Runway 32R (towards approach end of 32R) with another left onto Taxiway B as instructed when a Cessna C210 (C210), departed Runway 32R (approach end) without clearance. A Piper PA28 (PA28-2) had been cleared and was departing Runway 22 when the C210 started departure roll from 32R. The PA28-2 was airborne and crossed intersection of 22/32R first when the C210 was 2,500 feet from same intersection and also airborne. In addition, the PA28-1 was taxiing on 32R near Taxiway B when the C210 rotated within 1,500 feet horizontal. Once airborne the C210 flew parallel to left edge of runway and did not overfly the PA28-1. ADDITIONAL FACTOR: Training Environment ASF COMMENTS: When operating at a towered airport, the pilot must ensure a takeoff clearance is received prior to starting the takeoff roll. Visually check both ends for departing and arriving traffic prior to crossing a runway.
DATE: September 3, 2002 NARRATIVE: An unidentified white SUV type vehicle crossed Runway 22R via Taxiway N without clearance. B737, over landing threshold for Runway 22R executed a go-around, flying directly over the vehicle. Vertical separation was 50-100 feet. ASF COMMENTS: Runway incursions don't always occur between two aircraft. In this instance, a ground vehicle was the offender. Not all ground vehicle operators are aware of the special procedures necessary for safe operation on an airfield. When on final approach, the pilot should include the runway environment in his or her traffic scan.
DATE: July 31, 2002 NARRATIVE: A Cessna C182 was cleared to cross Runway 8/26 by Ground Control (GC) because Local Control (LC) had earlier approved GC use of the runway (LC activated the memory jogger light system indicating that Runway 8/26 was GC's). LC forgot Runway 8/26 was given to ground and cleared a BE90 to land Runway 8. Closest horizontal separation was 1,700 feet when N117PH was clearing the runway at Taxiway B. ASF COMMENTS: When operating in a towered airport environment, it is still up to the pilot to maintain a high level of alertness. Prior to crossing any runway, pilots should visually check for approaching and departing aircraft. ATC doesn�t miss often, but we should be ready to back them up.
DATE: August 4, 2002 NARRATIVE: Unmanned Cessna C172, crossed Runway 21, 1,500 feet from the approach end, after the pilot manually turned the propeller to start the aircraft. C172 crossed Runway 21, in front of a Beech BE90 that was landing Runway 21. The BE90 pilot saw the C172 and stomped on his brakes. The BE90 stopped 100 feet from where the C172 crossed. ASF COMMENTS: Pilots must ensure that their aircraft is properly secured prior to any hand propping operation. It is recommended that a qualified person be at the controls. Additionally, the airplane should be chocked, and the parking brake should be on.
DATE: July 11, 2002 NARRATIVE: A Beech BE1900D, after landing Runway 13 was given, and read back, hold short instructions for Runway 12L at Taxiway November. The B757-200, who had been holding in position at approach end Runway 12L, was cleared for takeoff. ATC then observed the BE1900D passed the hold lines Runway 12L at November with nose gear just short of the solid white runway edge line. The BE1900D had turned off the runway at a high rate of speed and could not stop at the hold lines. The BE1900D then observed the B757-200 approaching Taxiway N at a high rate of speed, so he broke hard to stop. ATC attempted to cancel takeoff clearance for the B757-200 but aircraft was accelerating past Taxiway November on the ground and did not respond. The B757-200 rotated just past Taxiway November. Closest proximity reported was approximately 10 feet horizontal. As reported by Central Region the AMASS did not alarm. ASF COMMENTS: Note the proximity of the parallel runway 13 to 12L. In retrospect, when faced with this runway - short taxiway - runway configuration, the exiting aircraft must be moving slowly when exiting the landing runway in order to hold short of the parallel. If you cannot comply with any hold short instructions, notify ATC IMMEDIATELY.
DATE: June 3, 2002 NARRATIVE: A Cessna 172 taxied onto and departed Runway 36 approach end without clearance. The C172 rotated between Taxiway B-1 and B-2 for Runway 36 and was between 150-200 AGL at the intersection of Runways 9 and 36. The CRJ2 departed Runway 9 from approach end after pilot confirmed he was cleared for departure. The CRJ2 rotated between Taxiway A and the intersection of 9/36, and passed under the C172 at the intersection of 9/36. Closest proximity reported was between 75-100 feet vertical. During this incident, there may have been a partially blocked radio transmission. ADDITIONAL FACTOR: Both aircraft had similar radio call signs. It's very easy to become confused during a situation such as this. ASF COMMENTS: Intersecting runways increase the potential for collision. Pilots must visually check for conflicting traffic regardless of clearance. Accidents in Sarasota, FL and Quincy, IL reinforce this point.
DATE: June 1, 2002 NARRATIVE: A Cessna 172, cleared to land Runway 31L, landed Runway 13L after acknowledging Runway 31L. A Lancair was landing Runway 31R at the same time. Both a/c came to a stop abeam Taxiway A4, facing each other. Closest proximity was less than 100 feet. ASF COMMENTS: Extra vigilance must be used when operating at an airport that has the 31/13 runway designation. It's easy to transpose the numbers. Parallel runway operations offer similar opportunities for confusion. Updated Thursday, October 27, 2005 3:30:15 PM
|
