Northeast Philadelphia Airport: Runway Incursions
71 reported incursions · 2 serious (Category A/B) · Philadelphia, PA
By year
- 20254
- 20243
- 20234
- 20223
- 20213
- 20207
- 20185
- 20174
- 20165
- 20152
- 20145
- 20132
- 20123
- 20112
- 20101
- 20092
- 20085
- 20072
- 20063
- 20053
- 20043
By severity category
- Category D — no immediate safety consequence35
- Category C — ample margin to avoid a collision22
- Other / pre-2008 classifications12
- Category B — significant separation loss2
By type
- Pilot deviation34
- Vehicle or pedestrian21
- Air traffic control12
- Other / unknown4
Serious incursions (Category A and B)
2018-06-15 · Northeast Philadelphia Airport · R22 (HELO) / PA44 · Category B
SUMMARY : HELICOPTER (A/C 1) WAS DOING PATTERN WORK ON TAXIWAY CHARLIE AND A PA44 (A/C 2) ON AN ILS PRACTICE APPROACH FOR RUNWAY 24 WAS DOING A MISSED APPROACH. THE HELICOPTER WAS CLEARED FOR THE OPTION ON TAXIWAY CHARLIE AND WAS NOT GIVEN RESTRICTIONS TO REMAIN SOUTHEAST OF RUNWAY 24. THE ONLY RESTRICTIONS THAT WERE GIVEN TO THE HELICOPTER WERE TO REMAIN EAST OF RUNWAY 33 AT ALL TIMES BY THE PREVIOUS CONTROLLER. THE CURRENT CONTROLLER INCORRECTLY ASSUMED THE HELICOPTER WAS RESTRICTED ON ALL RUNWAYS AFTER BRIEFING. N6PC WAS CLEARED FOR THE OPTION ON RUNWAY 24 AND N4SH WAS SITTING ON TAXIWAY CHARLIE WHEN A PHONE CALL WAS RECEIVED ON THE TOWER PHONE. IT WAS ANOTHER CONTROLLER WHO SAID GATE 17 WASN'T CLOSING BEHIND THEM. THE LOCAL CONTROLLER CALLED THE SUPERVISOR WHO TOLD THE CONTROLLER TO ADVISE GROUND CONTROL TO SEND AIRPORT SECURITY TO THE GATE 17. THERE WAS TRAINING ON GROUND CONTROL AND THEY WERE ADVISED TO DO SO. LOCAL CONTROL THEN SCANNED AND COULD SEE THAT N4SH WAS NORTHEAST OF RUNWAY 24 AND N6PC WAS ON THE UPWIND RUNWAY 24. N6PC ADVISED THE TOWER THAT THE HELICOPTER HAD CUT IN FRONT OF HIM, IT WAS VERY CLOSE AND THEY HAD TO MAKE AN EVASIVE MANEUVER IN ORDER TO AVOID THE HELICOPTER. QA SUMMARY : REVIEWED FALCON REPLAY, AUDIO, WEATHER, AND SEPARATION DETAILS. A/C 1 WAS CONDUCTING OPTION APPROACHES TO TAXIWAY CHARLIE (EAST AND PARALLEL TO RUNWAY 33). A POSITION RELIEF BRIEFING HAD BEEN COMPLETED AND THE RELIEVING CONTROLLER BELIEVED A/C 1 WAS RESTRICTED TO REMAIN EAST OF RUNWAY 33IN RIGHT HAND PATTERN. A/C 2 WAS MAKING A VFR APPROACH TO RUNWAY 24 AND CLEARED FOR THE OPTION. A/C 1 WAS ALSO CLEARED FOR THE OPTION TAXIWAY CHARLIE STILL ONLY RESTRICTED EAST OF RUNWAY 33. A/C 1 PASSED JUST IN FRONT OF A/C 2 OVER RUNWAY 24, LANDED AND COME TO A STOP NORTHEAST OF RUNWAY 24 ON TAXIWAY CHARLIE. THE PILOT OF A/C 2 STATED VIA TELEPHONE THAT THE HELICOPTER HAD BEEN OVER RUNWAY 24 AND THAT THE CLOSEST PROXIMITY ESTIMATED LESS THAN 100 FEET. VALIDATED LOSS. RIS FINDINGS : NA THE ORIGINAL FACILITY WRITE UP STATES THAT THE PILOT OF A/C 2 PA44 REPORTED TO THE TOWER THAT A/C 1 (HELO) ?CUT IN FRONT OF HIM, IT WAS VERY CLOSE AND THAT HE (A/C 2) MADE AN EVASIVE MANEUVER TO AVOID THE HELICOPTER AND THAT THE CLOSEST DISTANCE WAS LESS THAN 100FT
2013-07-24 · Northeast Philadelphia Airport · PA32 / C750 · RWY 24/33 · Category B
PA32 WAS ISSUED A LAHSO LANDING CLEARANCE ON RUNWAY 24. LAHSO CLEARANCE WAS ACKNOWLEDGED WITH AN ACCEPTANCE AS THE "ACTIVE" LAHSO AIRCRAFT. ATC INFORMED C750 OF THE LAHSO. C750 WAS GIVEN A FULL-LENGTH LANDING CLEARANCE TO RUNWAY 33 (PASSIVE LAHSO AIRCRAFT). ATC NOTICED THAT THE PA32 WAS ACCELERATING RATHER THAN DECELERATING AFTER TOUCHING DOWN ON RUNWAY 24, AND SUSPECTED THAT THE PA32 WAS NOT GOING TO COMPLY WITH THE LAHSO CLEARANCE. UPON HEARING ATC'S URGENT CALLS TO THE PA32 TO HOLD SHORT OF RUNWAY 33, THE C750 ASSUMED THE "ACTIVE" LAHSO ROLE AND TOOK EVASIVE ACTION, STOPPING SHORT OF RUNWAY 24 AT THE LAHSO MARKING AS THE PA32 PASSED THROUGH THE INTERSECTION. C750 RIGHT SEAT PILOT WAS OBSERVING THE PA32 AND PROMPTED THE PILOT FLYING TO ANTICIPATE HARD BRAKING TO AVOID ENTERING THE INTERSECTION. C750 STOPPED AT THE LAHSO LINE ON RUNWAY 33. ESTIMATED CLOSEST PROXIMITY WAS 215 FEET. WHEN PA32 REACHED TAXIWAY HOTEL IT VEERED OFF THE RUNWAY INTO THE GRASS ON THE NORTH SIDE AND CAME TO A STOP AND BECAME STUCK.
Counts are reported events, not a danger ranking. Before FY2008 the FAA used a narrower definition, so earlier years are not directly comparable.
Source: FAA Runway Safety (RWS) database, via ASIAS · United States Government public domain.