37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 593737 |
Time | |
Date | 200302 |
Day | Tue |
Place | |
Locale Reference | airport : bec.airport |
State Reference | KS |
Altitude | agl single value : 2000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : bec.tower |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : intermediate altitude climbout : initial |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : bec.tower |
Operator | other |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Route In Use | approach : traffic pattern |
Person 1 | |
Affiliation | other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : instrument pilot : multi engine pilot : cfi |
Experience | flight time last 90 days : 95 flight time total : 1790 flight time type : 6 |
ASRS Report | 593737 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : airborne less severe non adherence : far non adherence : published procedure |
Independent Detector | aircraft equipment : tcas other controllera other flight crewa |
Resolutory Action | controller : issued new clearance controller : separated traffic flight crew : took evasive action |
Supplementary | |
Problem Areas | Airspace Structure Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
After took delivery of a new beech premier 1, we took off out beech field (bec) in wichita, ks, the controller gave us our clearance to raleigh, nc, and cleared us to taxi over the runway. Few mins after, he told us to hold short to allow another premier to take off. After that traffic, he cleared us to get into position and hold. Then he asked if we have military traffic at 10 O'clock position, in sight. We answer yes. He said 'maintain visual separation, turn heading 110 degrees, clear for takeoff.' I applied power and started my takeoff roll. Just after getting airborne, we keep the runway heading until we crossed with the military tanker about 9 O'clock position, and we started the turn to 110 degrees. At that time, the controller told me that there was second traffic at 2 O'clock position and asked me if we have it in sight. The copilot answered no. After a few seconds, we called back and said now we have the traffic in sight. The controller said 'turn 110 degrees immediately.' we followed that instruction. A few seconds later, we got a TCASII RA and the second traffic, also a military tanker, approaching to mcconnel AFB, also did an evasive maneuver. I really think what caused that situation was a miscom and a hurry of the controller to get us out the airport soon. Our first clearance was to 3000 ft, which was in conflict with the tanker. Also, we were on an IFR flight plan, he cleared us for takeoff, then asked us to maintain visual separation with another traffic considering that a visual separation is at the PIC discretion. Then, if I am told to maintain visual separation with another traffic, how am I supposed to be able, in a matter of seconds, to determine the position of a third traffic and be responsible for evasive action while I'm being controled on an IFR flight plan?
Original NASA ASRS Text
Title: CONFLICT OCCURRED WHEN THE BEC LCL CTLR INSTRUCTED THE CREW OF A DEPARTING PREMIER BEECHCRAFT TO MAINTAIN VISUAL SEPARATION FROM MIL TANKER SE OF THE ARPT.
Narrative: AFTER TOOK DELIVERY OF A NEW BEECH PREMIER 1, WE TOOK OFF OUT BEECH FIELD (BEC) IN WICHITA, KS, THE CTLR GAVE US OUR CLRNC TO RALEIGH, NC, AND CLRED US TO TAXI OVER THE RWY. FEW MINS AFTER, HE TOLD US TO HOLD SHORT TO ALLOW ANOTHER PREMIER TO TAKE OFF. AFTER THAT TFC, HE CLRED US TO GET INTO POS AND HOLD. THEN HE ASKED IF WE HAVE MIL TFC AT 10 O'CLOCK POS, IN SIGHT. WE ANSWER YES. HE SAID 'MAINTAIN VISUAL SEPARATION, TURN HEADING 110 DEGS, CLR FOR TKOF.' I APPLIED PWR AND STARTED MY TKOF ROLL. JUST AFTER GETTING AIRBORNE, WE KEEP THE RWY HEADING UNTIL WE CROSSED WITH THE MIL TANKER ABOUT 9 O'CLOCK POS, AND WE STARTED THE TURN TO 110 DEGS. AT THAT TIME, THE CTLR TOLD ME THAT THERE WAS SECOND TFC AT 2 O'CLOCK POS AND ASKED ME IF WE HAVE IT IN SIGHT. THE COPLT ANSWERED NO. AFTER A FEW SECONDS, WE CALLED BACK AND SAID NOW WE HAVE THE TFC IN SIGHT. THE CTLR SAID 'TURN 110 DEGS IMMEDIATELY.' WE FOLLOWED THAT INSTRUCTION. A FEW SECONDS LATER, WE GOT A TCASII RA AND THE SECOND TFC, ALSO A MIL TANKER, APCHING TO MCCONNEL AFB, ALSO DID AN EVASIVE MANEUVER. I REALLY THINK WHAT CAUSED THAT SIT WAS A MISCOM AND A HURRY OF THE CTLR TO GET US OUT THE ARPT SOON. OUR FIRST CLRNC WAS TO 3000 FT, WHICH WAS IN CONFLICT WITH THE TANKER. ALSO, WE WERE ON AN IFR FLT PLAN, HE CLRED US FOR TKOF, THEN ASKED US TO MAINTAIN VISUAL SEPARATION WITH ANOTHER TFC CONSIDERING THAT A VISUAL SEPARATION IS AT THE PIC DISCRETION. THEN, IF I AM TOLD TO MAINTAIN VISUAL SEPARATION WITH ANOTHER TFC, HOW AM I SUPPOSED TO BE ABLE, IN A MATTER OF SECONDS, TO DETERMINE THE POS OF A THIRD TFC AND BE RESPONSIBLE FOR EVASIVE ACTION WHILE I'M BEING CTLED ON AN IFR FLT PLAN?
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.