ZKC controller described an operational deviation when adjacent sector/s failed to point out a fligh...

Narrative:

I was working sector 12 which controls FL240-FL340. I saw a pvd on my scope of a flight of 2/F16's; negative rvsm aircraft. The flight was level at FL350 northwest of spi VORTAC. I don't know if chicago center sent me the pvd or the super high above me; sector 98. Sector 98 informed me the flight was also nonstandard flight of two F16's and one mile in-trail in addition to being negative rvsm. I was never called for a point out by either hannah city or roberts sectors of chicago center. Since the flight was level at FL350 and negative rvsm; I have to protect airspace in my stratum for that flight and was deviated by not receiving a point out. Traffic was not delayed in any way. There was not a loss of separation with any aircraft in my sector involving the F16 flight. Recommendation; follow through with procedure and point out negative rvsm aircraft to all affected sectors/ centers. Also; chicago simply could have climbed the flight to FL370 and only had to coordinate with the super high; sector 98; about the flight.

Original NASA ASRS Text

Title: ZKC controller described an operational deviation when adjacent sector/s failed to point out a flight of non standard/non RVSM military aircraft that required additional separation.

Narrative: I was working Sector 12 which controls FL240-FL340. I saw a PVD on my scope of a flight of 2/F16's; negative RVSM aircraft. The flight was level at FL350 northwest of SPI VORTAC. I don't know if Chicago Center sent me the PVD or the super high above me; Sector 98. Sector 98 informed me the flight was also nonstandard flight of two F16's and one mile in-trail in addition to being negative RVSM. I was never called for a point out by either Hannah City or Roberts Sectors of Chicago Center. Since the flight was level at FL350 and negative RVSM; I have to protect airspace in my stratum for that flight and was deviated by not receiving a point out. Traffic was not delayed in any way. There was not a loss of separation with any aircraft in my sector involving the F16 flight. Recommendation; follow through with procedure and point out negative RVSM aircraft to all affected sectors/ centers. Also; Chicago simply could have climbed the flight to FL370 and only had to coordinate with the super high; Sector 98; about the flight.

Data retrieved from NASA's ASRS site as of April 2012 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.

Attributes
ACN	883693
Time
Date	201004
Local Time Of Day	1801-2400
Place
Locale Reference	ZKC.ARTCC
State Reference	KS
Aircraft 1
Make Model Name	Lockheed Corp Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	None
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

ZKC controller described an operational deviation when adjacent sector/s failed to point out a flight of non standard/non rvsm military aircraft that required additional separation.