37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 481279 |
Time | |
Date | 200008 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : sus.airport |
State Reference | MO |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : sus.tower |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : initial climbout : takeoff ground : takeoff roll ground : taxi |
Route In Use | departure other |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : first officer |
Qualification | pilot : private |
Experience | flight time last 90 days : 16 flight time total : 175 flight time type : 54 |
ASRS Report | 481279 |
Person 2 | |
Affiliation | other |
Function | observation : company check pilot |
Qualification | pilot : private |
Events | |
Anomaly | airspace violation : entry incursion : runway non adherence : published procedure non adherence : far |
Independent Detector | other controllera other controllerb |
Resolutory Action | controller : issued advisory |
Consequence | faa : investigated |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On the evening of aug/xa/00, my safety pilot and I began our return trip to smd from sus. After the preflight, we taxied to the end of runway 8R and completed the run-up. While completing the run-up, pilot B set the radios to 120.9. We called departing runway 8R, then we taxied onto the runway and began our departure. About 2 mins after calling departure the pattern to the east, we heard another aircraft on the same frequency talking to downtown-parks traffic. By that time we were nearing the airspace over downtown-parks, and since we were under the false assumption that the sus tower was already closed, we failed to make a call back to sus traffic. We continued out of the st louis area and on toward indianapolis to refuel. When we contacted ind approach they informed us we were to call the airport supervisor in st louis. Upon returning his call, he informed us that we had departed an airport with an operating tower without contacting them. It was then that we realized that we had incorrectly ascertained that the tower was closed because we used information from the downtown-parks airport when reading the AFD. Therefore, we not only thought the tower was closed, but we were using the wrong CTAF. There were several factors that contributed to our failure to communicate with the proper controling agency. The first of which was the lack of attention that ws paid to, or failure in doublechking all frequencys that were to be used in-flight. Another contributing factor was the late hour which may have caused us to be less than thorough. The area in which we were flying was also unfamiliar to both of us. In retrospect, we should have doublechked using more than 1 source, ie, AFD, sectional charts, while en route -- especially not being familiar with the area.
Original NASA ASRS Text
Title: SMA PLT DEPARTS SUS WITHOUT CLRNC, BELIEVING TWR WAS CLOSED.
Narrative: ON THE EVENING OF AUG/XA/00, MY SAFETY PLT AND I BEGAN OUR RETURN TRIP TO SMD FROM SUS. AFTER THE PREFLT, WE TAXIED TO THE END OF RWY 8R AND COMPLETED THE RUN-UP. WHILE COMPLETING THE RUN-UP, PLT B SET THE RADIOS TO 120.9. WE CALLED DEPARTING RWY 8R, THEN WE TAXIED ONTO THE RWY AND BEGAN OUR DEP. ABOUT 2 MINS AFTER CALLING DEP THE PATTERN TO THE E, WE HEARD ANOTHER ACFT ON THE SAME FREQ TALKING TO DOWNTOWN-PARKS TFC. BY THAT TIME WE WERE NEARING THE AIRSPACE OVER DOWNTOWN-PARKS, AND SINCE WE WERE UNDER THE FALSE ASSUMPTION THAT THE SUS TWR WAS ALREADY CLOSED, WE FAILED TO MAKE A CALL BACK TO SUS TFC. WE CONTINUED OUT OF THE ST LOUIS AREA AND ON TOWARD INDIANAPOLIS TO REFUEL. WHEN WE CONTACTED IND APCH THEY INFORMED US WE WERE TO CALL THE ARPT SUPVR IN ST LOUIS. UPON RETURNING HIS CALL, HE INFORMED US THAT WE HAD DEPARTED AN ARPT WITH AN OPERATING TWR WITHOUT CONTACTING THEM. IT WAS THEN THAT WE REALIZED THAT WE HAD INCORRECTLY ASCERTAINED THAT THE TWR WAS CLOSED BECAUSE WE USED INFO FROM THE DOWNTOWN-PARKS ARPT WHEN READING THE AFD. THEREFORE, WE NOT ONLY THOUGHT THE TWR WAS CLOSED, BUT WE WERE USING THE WRONG CTAF. THERE WERE SEVERAL FACTORS THAT CONTRIBUTED TO OUR FAILURE TO COMMUNICATE WITH THE PROPER CTLING AGENCY. THE FIRST OF WHICH WAS THE LACK OF ATTN THAT WS PAID TO, OR FAILURE IN DOUBLECHKING ALL FREQS THAT WERE TO BE USED INFLT. ANOTHER CONTRIBUTING FACTOR WAS THE LATE HR WHICH MAY HAVE CAUSED US TO BE LESS THAN THOROUGH. THE AREA IN WHICH WE WERE FLYING WAS ALSO UNFAMILIAR TO BOTH OF US. IN RETROSPECT, WE SHOULD HAVE DOUBLECHKED USING MORE THAN 1 SOURCE, IE, AFD, SECTIONAL CHARTS, WHILE ENRTE -- ESPECIALLY NOT BEING FAMILIAR WITH THE AREA.
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.