Feb 27, 2018 - RAA, SWAPA, Jeppesen Sanderson, Inc. Info: From: ORF Runway 05 Taxiway ... ACN: 1508804. Time. Date: 2018
2/27/2018
FOR YOUR INFORMATION
2018-43/5-13 1508804
To:
Airport Manager, Norfolk International Airport, (ORF), VA.
Info:
FAA (AAS-300, AVP-1, AVP-200, AJI-144, AJV-5, AEA-600, AFS-280, AFS-200, Director of Air Traffic Operations ESA South), A4A, AAAE, ALPA, AOPA, APA, ASAP, CAPA, ATSAP, ATSG, IATA, IBT, ICAO, ICASS, IFALPA, IPA, NATCA, NBAA, NTSB, RAA, SWAPA, Jeppesen Sanderson, Inc.
From: Linda J. Connell, Director
NASA Aviation Safety Reporting System Re:
ORF Runway 05 Taxiway Signage
We recently received an ASRS report describing a safety concern that may involve your area of operational responsibility. We do not have sufficient details to assess either the factual accuracy or possible gravity of the report. It is our policy to relay the reported information to the appropriate authority for evaluation and any necessary follow-up. We feel you should be aware of the enclosed deidentified report.
To properly assess the usefulness of our alert message service, we would appreciate it if you would take the time to give us your feedback on the value of the information that we have provided. Please contact Dennis Doyle at (408) 541-2831 or email at
[email protected]
Aviation Safety Reporting System P.O. Box 189 | Moffett Field, CA | 94035-0189
ACN: 1508804 Time Date: 201801 Local Time Of Day: 0601-1200 Place Locale Reference.Airport: ORF.Airport State Reference: VA Altitude.AGL.Single Value: 0 Environment Flight Conditions: VMC Aircraft 1 ATC / Advisory.Tower: ORF Make Model Name: Regional Jet 900 (CRJ900) Person 1 Function.Flight Crew: Captain Function.Flight Crew: Pilot Not Flying ASRS Report Number: 1508804 Events Anomaly.Deviation - Procedural: Published Material / Policy Anomaly.Ground Incursion: Runway Detector.Person: Flight Crew Result.Flight Crew: Requested ATC Assistance / Clarification Narrative 1 Taxi to Runway 05. While taxiing to the far end of Runway 05 I rolled past the hold short line by approximately 30 feet. I recognized the error stopped the aircraft and asked the FO to notify Tower of our position. Tower acknowledged by stating "no problem you're next to go." There was no landing or departing traffic through this event, up to and including our departure. Leading to this event was the Jeppesen chart which appeared to indicate a holding bay where we were located. We had parked on the far north side of this area so that traffic potentially behind us could pass us while we waited for our wheels up time. In addition there was no runway intersection signage installed adjacent to the runway, nor was there a painted Runway 05 intersection runway marking where we exited the taxiway (though there was to my far right which I did not see). Also, Runway 05, at this end, has a displaced threshold with markings that did not appear to be a runway from our location on the ground. Finally, the south end of Taxiway J appeared to be the actual runway based on the visual cues outside the window, including the widened part of Taxiway J at that location, and the Jeppesen chart depiction of what looked like a hold bay where we were proceeding. This is an excellent example of where a Hot Spot should be depicted to warn crews of misleading visual cues of where Runway 05 is actually located. Synopsis CRJ-900 Captain reported a runway incursion at ORF due to a lack of runway markings and signage.
