37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 482585 |
Time | |
Date | 200008 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : ilm.airport |
State Reference | NC |
Altitude | agl bound lower : 0 agl bound upper : 500 |
Environment | |
Flight Conditions | VMC |
Weather Elements | other |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : ilm.tower |
Operator | general aviation : personal |
Make Model Name | Skylane 182/RG Turbo Skylane/RG |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff ground : takeoff roll |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : ilm.tower |
Operator | general aviation : personal |
Make Model Name | Skylane 182/RG Turbo Skylane/RG |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff |
Route In Use | departure : on vectors |
Flight Plan | VFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : radar pilot : private |
Experience | controller military : 4 controller non radar : 4 controller radar : 8 controller time certified in position1 : 4 flight time total : 85 |
ASRS Report | 482585 |
Person 2 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : commercial pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 14 flight time total : 6971 flight time type : 490 |
ASRS Report | 481606 |
Events | |
Anomaly | conflict : ground critical inflight encounter : weather non adherence : required legal separation non adherence : published procedure |
Independent Detector | other controllera other flight crewa |
Consequence | faa : reviewed incident with flight crew faa : investigated |
Miss Distance | horizontal : 0 vertical : 500 |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
Aircraft Y called ready for departure on runway 17, and I instructed him to hold short. Aircraft X called ready for departure on runway 35. And instructed him to hold short. I instructed aircraft Y to taxi into position and hold runway 17 (due to traffic on runway). When the runway 24 operation was complete, I instructed aircraft Y to fly runway heading and cleared him for takeoff on runway 17. Aircraft Y was airborne (climbing), and no lower than 500 ft AGL, when I observed a cessna at taxi speed on runway 35 abeam the tower. Supplemental information from acn 481606: I requested my IFR clearance to chapel hill (igx). After reading back the clearance, I advised ground control I was ready to taxi. I requested a takeoff on runway 35 if traffic permitted. I heard an aircraft request and receive clearance to taxi to runway 17. Ground control then called me to verify my call sign. When the runup was complete, I changed to wilmington tower frequency and began to taxi into a position short of runway 35. Within seconds, the tower cleared to fly runway heading and cleared for takeoff on runway 35. I repeated to tower that I was cleared for takeoff on runway 35 and to fly runway heading. (I always repeat instructions and clrncs to make sure that there can be no misunderstanding.) there was no questioning of my readback. I taxied onto the runway and began my takeoff. I was just a few hundred ft down the runway when I spotted an aircraft that was airborne several hundred ft in the air, climbing on a heading of approximately 160 degrees on a course well to the left of runway 17 and not a threat to me on my takeoff roll or climb out course. My immediate thought was that the aircraft was on a missed approach or a go around. The aircraft continued to climb out on a southeastern course, and was past me before I had rolled 2000 ft. After I was airborne and climbing out, the tower gave me instructions to turn left on a westward track and informed me that I was to call the tower supervisor upon landing. Even though I had received a clearance to my destination, I elected to return to the ramp immediately to call the tower supervisor. It was not until calling the supervisor that I became aware that another aircraft had taken off on runway 17. At that time, the supervisor told me that he had reviewed the tape 4 times and that there were some problems in the tower. When queried further, he acknowledged that even though I was stepped on in my transmission, I definitely had called the tower to acknowledge a clearance that I was cleared for takeoff on runway 35 and that call was never challenged. He also noted that the situation was aggravated by the fact that the operator was talking to several aircraft that had very similar call signs.
Original NASA ASRS Text
Title: ILM CTLR INVOLVED IN OPERROR WHEN 2 C182'S DEPART FROM DIFFERENT RWYS SIMULTANEOUSLY WITH SIMILAR CALL SIGNS.
Narrative: ACFT Y CALLED READY FOR DEP ON RWY 17, AND I INSTRUCTED HIM TO HOLD SHORT. ACFT X CALLED READY FOR DEP ON RWY 35. AND INSTRUCTED HIM TO HOLD SHORT. I INSTRUCTED ACFT Y TO TAXI INTO POS AND HOLD RWY 17 (DUE TO TFC ON RWY). WHEN THE RWY 24 OP WAS COMPLETE, I INSTRUCTED ACFT Y TO FLY RWY HDG AND CLRED HIM FOR TKOF ON RWY 17. ACFT Y WAS AIRBORNE (CLBING), AND NO LOWER THAN 500 FT AGL, WHEN I OBSERVED A CESSNA AT TAXI SPD ON RWY 35 ABEAM THE TWR. SUPPLEMENTAL INFO FROM ACN 481606: I REQUESTED MY IFR CLRNC TO CHAPEL HILL (IGX). AFTER READING BACK THE CLRNC, I ADVISED GND CTL I WAS READY TO TAXI. I REQUESTED A TKOF ON RWY 35 IF TFC PERMITTED. I HEARD AN ACFT REQUEST AND RECEIVE CLRNC TO TAXI TO RWY 17. GND CTL THEN CALLED ME TO VERIFY MY CALL SIGN. WHEN THE RUNUP WAS COMPLETE, I CHANGED TO WILMINGTON TWR FREQ AND BEGAN TO TAXI INTO A POS SHORT OF RWY 35. WITHIN SECONDS, THE TWR CLRED TO FLY RWY HDG AND CLRED FOR TKOF ON RWY 35. I REPEATED TO TWR THAT I WAS CLRED FOR TKOF ON RWY 35 AND TO FLY RWY HDG. (I ALWAYS REPEAT INSTRUCTIONS AND CLRNCS TO MAKE SURE THAT THERE CAN BE NO MISUNDERSTANDING.) THERE WAS NO QUESTIONING OF MY READBACK. I TAXIED ONTO THE RWY AND BEGAN MY TKOF. I WAS JUST A FEW HUNDRED FT DOWN THE RWY WHEN I SPOTTED AN ACFT THAT WAS AIRBORNE SEVERAL HUNDRED FT IN THE AIR, CLBING ON A HDG OF APPROX 160 DEGS ON A COURSE WELL TO THE L OF RWY 17 AND NOT A THREAT TO ME ON MY TKOF ROLL OR CLB OUT COURSE. MY IMMEDIATE THOUGHT WAS THAT THE ACFT WAS ON A MISSED APCH OR A GAR. THE ACFT CONTINUED TO CLB OUT ON A SOUTHEASTERN COURSE, AND WAS PAST ME BEFORE I HAD ROLLED 2000 FT. AFTER I WAS AIRBORNE AND CLBING OUT, THE TWR GAVE ME INSTRUCTIONS TO TURN L ON A WESTWARD TRACK AND INFORMED ME THAT I WAS TO CALL THE TWR SUPVR UPON LNDG. EVEN THOUGH I HAD RECEIVED A CLRNC TO MY DEST, I ELECTED TO RETURN TO THE RAMP IMMEDIATELY TO CALL THE TWR SUPVR. IT WAS NOT UNTIL CALLING THE SUPVR THAT I BECAME AWARE THAT ANOTHER ACFT HAD TAKEN OFF ON RWY 17. AT THAT TIME, THE SUPVR TOLD ME THAT HE HAD REVIEWED THE TAPE 4 TIMES AND THAT THERE WERE SOME PROBS IN THE TWR. WHEN QUERIED FURTHER, HE ACKNOWLEDGED THAT EVEN THOUGH I WAS STEPPED ON IN MY XMISSION, I DEFINITELY HAD CALLED THE TWR TO ACKNOWLEDGE A CLRNC THAT I WAS CLRED FOR TKOF ON RWY 35 AND THAT CALL WAS NEVER CHALLENGED. HE ALSO NOTED THAT THE SIT WAS AGGRAVATED BY THE FACT THAT THE OPERATOR WAS TALKING TO SEVERAL ACFT THAT HAD VERY SIMILAR CALL SIGNS.
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.