MD80 flight crew initiates evasive maneuver due to TCASII RA when ZKC does not issue traffic alert.

Attributes
ACN	475930
Time
Date	200005
Day	Mon
Local Time Of Day	1201 To 1800
Place
State Reference	MO
Altitude	msl bound lower : 17000 msl bound upper : 18000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zkc.artcc tracon : i90.tracon
Operator	common carrier : air carrier
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : vacating altitude
Route In Use	departure sid : n/s
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zkc.artcc
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	cruise : level
Flight Plan	VFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 210 flight time total : 11000 flight time type : 7000
ASRS Report	475930
Person 2
Qualification	pilot : private
Events
Anomaly	altitude deviation : undershoot conflict : airborne less severe non adherence : published procedure
Independent Detector	atc equipment other atc equipment : zkc radar aircraft equipment : tcas other controllera other flight crewa
Resolutory Action	controller : issued advisory flight crew : took evasive action flight crew : took precautionary avoidance action
Consequence	faa : investigated faa : reviewed incident with flight crew
Miss Distance	horizontal : 11580 vertical : 200
Supplementary
Problem Areas	Airspace Structure Flight Crew Human Performance ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

Departing stl on IFR flight plan to sgf, ZKC cleared us to climb to FL180. Shortly after that, I noticed a target on our TCASII closing on us. By the time I was able to assess, he was at FL180 or about (actually 17500 ft). He was 8 mi away. I asked ATC if they had a target at our 2 O'clock and 8 mi. They said 'yes, he is at 17500 ft.' at about this time, the target entered our 2 mi range on TCASII and we got an RA at about 17000 ft and leveled off. I saw the aircraft go by when it was at the 2:30 O'clock position. I told ATC that it was very close to us and they replied, '...17500 ft is a VFR altitude....' there were other human factors involved in this such as: training (ATC), high volume, complexity of situation (arrs to stl just were shut off) and a death in trainer's family. The management agreed with me that traffic should have been issued, but not required since other aircraft were VFR and not talking to anybody! With the increase of regional jets and other traffic, forcing executive and 'fractionals' jets to go VFR below FL180, I see a big problem arising. Something needs to be done about traffic at VFR altitudes!

Original NASA ASRS Text

Title: MD80 FLC INITIATES EVASIVE MANEUVER DUE TO TCASII RA WHEN ZKC DOES NOT ISSUE TFC ALERT.

Narrative: DEPARTING STL ON IFR FLT PLAN TO SGF, ZKC CLRED US TO CLB TO FL180. SHORTLY AFTER THAT, I NOTICED A TARGET ON OUR TCASII CLOSING ON US. BY THE TIME I WAS ABLE TO ASSESS, HE WAS AT FL180 OR ABOUT (ACTUALLY 17500 FT). HE WAS 8 MI AWAY. I ASKED ATC IF THEY HAD A TARGET AT OUR 2 O'CLOCK AND 8 MI. THEY SAID 'YES, HE IS AT 17500 FT.' AT ABOUT THIS TIME, THE TARGET ENTERED OUR 2 MI RANGE ON TCASII AND WE GOT AN RA AT ABOUT 17000 FT AND LEVELED OFF. I SAW THE ACFT GO BY WHEN IT WAS AT THE 2:30 O'CLOCK POS. I TOLD ATC THAT IT WAS VERY CLOSE TO US AND THEY REPLIED, '...17500 FT IS A VFR ALT....' THERE WERE OTHER HUMAN FACTORS INVOLVED IN THIS SUCH AS: TRAINING (ATC), HIGH VOLUME, COMPLEXITY OF SIT (ARRS TO STL JUST WERE SHUT OFF) AND A DEATH IN TRAINER'S FAMILY. THE MGMNT AGREED WITH ME THAT TFC SHOULD HAVE BEEN ISSUED, BUT NOT REQUIRED SINCE OTHER ACFT WERE VFR AND NOT TALKING TO ANYBODY! WITH THE INCREASE OF REGIONAL JETS AND OTHER TFC, FORCING EXECUTIVE AND 'FRACTIONALS' JETS TO GO VFR BELOW FL180, I SEE A BIG PROB ARISING. SOMETHING NEEDS TO BE DONE ABOUT TFC AT VFR ALTS!

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.