37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 559708 |
Time | |
Date | 200209 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : csg.airport |
State Reference | GA |
Altitude | agl single value : 25 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : corporate |
Make Model Name | HS 125 Series 1-600 |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff ground : takeoff roll |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 120 flight time total : 4000 flight time type : 1200 |
ASRS Report | 559708 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : commercial pilot : private |
Experience | flight time last 90 days : 150 flight time total : 7000 flight time type : 1500 |
ASRS Report | 562254 |
Events | |
Anomaly | conflict : ground critical incursion : runway non adherence : far non adherence : published procedure other anomaly other other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact none taken : insufficient time |
Consequence | Other |
Miss Distance | horizontal : 500 vertical : 0 |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airport ATC Facility Environmental Factor |
Primary Problem | Environmental Factor |
Narrative:
I was acting as first officer of a part 91 repos leg from csg to bct. We taxied from the FBO to runway 6. While dividing my time between runway checklists and looking for other taxiing traffic, the captain mentioned that there was a C172 running up at the end of the other runway (runway 31). At the time the wind was calm, the tower was not yet in operation, so we elected to use runway 6 -- the longer of the 2 runways. I radioed our intentions to use runway 6 on the CTAF. After calling atl approach for our outbound IFR release, I returned to the CTAF and announced that hawker X was taking runway 6 for departure. I heard no conflicting traffic on the frequency. However, I could not see the end of the runway where we had seen the C172 (runway 31) due to trees and terrain. We continued with the takeoff run and lifted off midfield. While climbing out normally, I heard the cessna call on the CTAF, 'hawker, did you call departing runway 6?' I replied that we had called. He replied, 'we just lifted off runway 31 and did not hear your call.' 'there was a near mishap there.' I relayed my apologies and announced that we were departing the pattern. In retrospect, it is obvious that there was a lack of communications that led to this incident. As the PNF, I clearly should have attempted to contact the C172 which was pointed out on the opposing runway instead of assuming that he was still running up. Waiting only a min or 2 to confirm the other aircraft's intentions would have been prudent in this situation. It is also worthy to note that neither the captain nor I saw the C172 taking off from the other runway, so I am unable to report how close in actuality he came to our aircraft. I heard no other communications from the other aircraft, therefore, I was not aware of his proximity. Having the columbus tower extend its operations to open earlier than XA00 would have made this incident a non event. From my observations, this airport is quite busy even before the tower opens. Supplemental information from acn 562254: the first officer switched frequencys to atl approach to obtain an IFR release. When released into the airspace, I moved the aircraft into position and hold where the line-up checklist was completed and the first officer announced our intention to take off. We did not hear any other traffic on or in the vicinity of the airport and takeoff was initiated. At this point, I cannot confirm whether the first officer announced our intention to take off on atl approach or on CTAF. Clearly, there was a communications failure between the 2 incident aircraft. Both crews should have waited another 10 mins prior to taxi. With the tower open, the incident would have been averted. Csg airport management needs to review/adjust the current control tower operating hours. Also, the trees that serve to mutually obstruct the view of one approach end from the other should be removed. After reflecting upon the mission, it is clear to me that there was a self imposed sense of urgency on the part of the crew of aircraft X. I should not have allowed this. Things were going smoothly and I could have better controled the cockpit environment by slowing the pace.
Original NASA ASRS Text
Title: NEAR GND COLLISION BTWN AN H25B AND A C172 ON TKOF FROM INTERSECTING RWYS WHEN TWR WAS CLOSED AT CSG, GA.
Narrative: I WAS ACTING AS FO OF A PART 91 REPOS LEG FROM CSG TO BCT. WE TAXIED FROM THE FBO TO RWY 6. WHILE DIVIDING MY TIME BTWN RWY CHKLISTS AND LOOKING FOR OTHER TAXIING TFC, THE CAPT MENTIONED THAT THERE WAS A C172 RUNNING UP AT THE END OF THE OTHER RWY (RWY 31). AT THE TIME THE WIND WAS CALM, THE TWR WAS NOT YET IN OP, SO WE ELECTED TO USE RWY 6 -- THE LONGER OF THE 2 RWYS. I RADIOED OUR INTENTIONS TO USE RWY 6 ON THE CTAF. AFTER CALLING ATL APCH FOR OUR OUTBOUND IFR RELEASE, I RETURNED TO THE CTAF AND ANNOUNCED THAT HAWKER X WAS TAKING RWY 6 FOR DEP. I HEARD NO CONFLICTING TFC ON THE FREQ. HOWEVER, I COULD NOT SEE THE END OF THE RWY WHERE WE HAD SEEN THE C172 (RWY 31) DUE TO TREES AND TERRAIN. WE CONTINUED WITH THE TKOF RUN AND LIFTED OFF MIDFIELD. WHILE CLBING OUT NORMALLY, I HEARD THE CESSNA CALL ON THE CTAF, 'HAWKER, DID YOU CALL DEPARTING RWY 6?' I REPLIED THAT WE HAD CALLED. HE REPLIED, 'WE JUST LIFTED OFF RWY 31 AND DID NOT HEAR YOUR CALL.' 'THERE WAS A NEAR MISHAP THERE.' I RELAYED MY APOLOGIES AND ANNOUNCED THAT WE WERE DEPARTING THE PATTERN. IN RETROSPECT, IT IS OBVIOUS THAT THERE WAS A LACK OF COMS THAT LED TO THIS INCIDENT. AS THE PNF, I CLRLY SHOULD HAVE ATTEMPTED TO CONTACT THE C172 WHICH WAS POINTED OUT ON THE OPPOSING RWY INSTEAD OF ASSUMING THAT HE WAS STILL RUNNING UP. WAITING ONLY A MIN OR 2 TO CONFIRM THE OTHER ACFT'S INTENTIONS WOULD HAVE BEEN PRUDENT IN THIS SIT. IT IS ALSO WORTHY TO NOTE THAT NEITHER THE CAPT NOR I SAW THE C172 TAKING OFF FROM THE OTHER RWY, SO I AM UNABLE TO RPT HOW CLOSE IN ACTUALITY HE CAME TO OUR ACFT. I HEARD NO OTHER COMS FROM THE OTHER ACFT, THEREFORE, I WAS NOT AWARE OF HIS PROX. HAVING THE COLUMBUS TWR EXTEND ITS OPS TO OPEN EARLIER THAN XA00 WOULD HAVE MADE THIS INCIDENT A NON EVENT. FROM MY OBSERVATIONS, THIS ARPT IS QUITE BUSY EVEN BEFORE THE TWR OPENS. SUPPLEMENTAL INFO FROM ACN 562254: THE FO SWITCHED FREQS TO ATL APCH TO OBTAIN AN IFR RELEASE. WHEN RELEASED INTO THE AIRSPACE, I MOVED THE ACFT INTO POS AND HOLD WHERE THE LINE-UP CHKLIST WAS COMPLETED AND THE FO ANNOUNCED OUR INTENTION TO TAKE OFF. WE DID NOT HEAR ANY OTHER TFC ON OR IN THE VICINITY OF THE ARPT AND TKOF WAS INITIATED. AT THIS POINT, I CANNOT CONFIRM WHETHER THE FO ANNOUNCED OUR INTENTION TO TAKE OFF ON ATL APCH OR ON CTAF. CLRLY, THERE WAS A COMS FAILURE BTWN THE 2 INCIDENT ACFT. BOTH CREWS SHOULD HAVE WAITED ANOTHER 10 MINS PRIOR TO TAXI. WITH THE TWR OPEN, THE INCIDENT WOULD HAVE BEEN AVERTED. CSG ARPT MGMNT NEEDS TO REVIEW/ADJUST THE CURRENT CTL TWR OPERATING HRS. ALSO, THE TREES THAT SERVE TO MUTUALLY OBSTRUCT THE VIEW OF ONE APCH END FROM THE OTHER SHOULD BE REMOVED. AFTER REFLECTING UPON THE MISSION, IT IS CLR TO ME THAT THERE WAS A SELF IMPOSED SENSE OF URGENCY ON THE PART OF THE CREW OF ACFT X. I SHOULD NOT HAVE ALLOWED THIS. THINGS WERE GOING SMOOTHLY AND I COULD HAVE BETTER CTLED THE COCKPIT ENVIRONMENT BY SLOWING THE PACE.
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.