37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 163458 |
Time | |
Date | 199011 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : csg |
State Reference | GA |
Altitude | msl bound lower : 2300 msl bound upper : 2300 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : csg |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Fixed Gear |
Flight Phase | cruise other |
Flight Plan | VFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Experience | flight time last 90 days : 46 flight time total : 416 flight time type : 30 |
ASRS Report | 163458 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | non adherence : far non adherence : published procedure other anomaly other |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were nwbnd on V321 southeast of the columbus, GA, arsa. 21 mi out, radio contact was made with columbus approach stating our position, course, and altitude. Columbus provided a squawk code which was entered. Columbus approach had a heavy workload and there was a delay acknowledging radar contact. We were concerned about the delay since we were approaching a restr area controled by columbus ATC. Columbus then contacted us verifying radar contact and advised that we were in the restr area and a course of 180 degrees was required to clear the area. A turn to 180 degrees was initiated immediately and acknowledged to columbus. Within 30 seconds, we started receiving vectors turning us to west indicating that we had cleared the restr area and that our penetration into the restr area wasn't much more than 1 mi. Due the special nature of the columbus arsa, the normal procedure of radio contact at a 20 mi distance is insufficient when approaching from the southeast. It does not allow for small navigational error or unavoidable delays caused by heavy workloads by the controller. We will try to establish radio contact 30 mi out in future flts to provide more time for vectoring.
Original NASA ASRS Text
Title: SMA PENETRATES RESTRICTED AREA R3002A WITHOUT AUTH.
Narrative: WE WERE NWBND ON V321 SE OF THE COLUMBUS, GA, ARSA. 21 MI OUT, RADIO CONTACT WAS MADE WITH COLUMBUS APCH STATING OUR POS, COURSE, AND ALT. COLUMBUS PROVIDED A SQUAWK CODE WHICH WAS ENTERED. COLUMBUS APCH HAD A HVY WORKLOAD AND THERE WAS A DELAY ACKNOWLEDGING RADAR CONTACT. WE WERE CONCERNED ABOUT THE DELAY SINCE WE WERE APCHING A RESTR AREA CTLED BY COLUMBUS ATC. COLUMBUS THEN CONTACTED US VERIFYING RADAR CONTACT AND ADVISED THAT WE WERE IN THE RESTR AREA AND A COURSE OF 180 DEGS WAS REQUIRED TO CLR THE AREA. A TURN TO 180 DEGS WAS INITIATED IMMEDIATELY AND ACKNOWLEDGED TO COLUMBUS. WITHIN 30 SECS, WE STARTED RECEIVING VECTORS TURNING US TO W INDICATING THAT WE HAD CLRED THE RESTR AREA AND THAT OUR PENETRATION INTO THE RESTR AREA WASN'T MUCH MORE THAN 1 MI. DUE THE SPECIAL NATURE OF THE COLUMBUS ARSA, THE NORMAL PROC OF RADIO CONTACT AT A 20 MI DISTANCE IS INSUFFICIENT WHEN APCHING FROM THE SE. IT DOES NOT ALLOW FOR SMALL NAVIGATIONAL ERROR OR UNAVOIDABLE DELAYS CAUSED BY HVY WORKLOADS BY THE CTLR. WE WILL TRY TO ESTABLISH RADIO CONTACT 30 MI OUT IN FUTURE FLTS TO PROVIDE MORE TIME FOR VECTORING.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.