Sus local controller voiced concern regard the newly adopted ICAO format for filing flight plan info...

Narrative:

In the last few weeks since the new ICAO flight plan format has started; we have had issues with flight plans requesting the gateway 4 departure off of sus that have been filed through commercial operator flight planning service. This has happened at least 8 times that I have witnessed. 5 of the times I know the commercial operator filed the flight plan and the other 3 occurred before I idented that this is a recurring problem. There are 3 issues that I see and they are always the same. 1) the pilot is requesting the gateway 4 departure; but it is not being entered into the flight plan. Instead; there is a statement placed in the remarks section of the flight plan stating 'request GATEWY4.' I have seen ICAO formatted flight plans that contain the gateway 4 departure in the flight plan route. I do not know who filed these correctly. 2) the flight plan route always has blv as the first fix east of sus in the flight plan. Today's clearance was 'ksus..blv..rod..kcvg.' blv is an airport and not a navigation fix. Aircraft en route should be navigating to navigation fixes and not to airports along the route. 3) the flight plan indicates full route clearance; but this indication is buried in the remarks. Today's remarks were: 'aircraft X irmk/FRC0REQUEST GATEWY4.' this has almost and most certainly will cause errors in the national airspace system. It is extremely easy to overlook the frc when it is buried in the remarks. If the flight plan had been entered properly; a full route clearance would not be necessary.

Original NASA ASRS Text

Title: SUS LCL CTLR VOICED CONCERN REGARD THE NEWLY ADOPTED ICAO FORMAT FOR FILING FLT PLAN INFO; ALLEGING SID IS NOT INCLUDED IN RTE BUT IN REMARKS.

Narrative: IN THE LAST FEW WKS SINCE THE NEW ICAO FLT PLAN FORMAT HAS STARTED; WE HAVE HAD ISSUES WITH FLT PLANS REQUESTING THE GATEWAY 4 DEP OFF OF SUS THAT HAVE BEEN FILED THROUGH COMMERCIAL OPERATOR FLT PLANNING SVC. THIS HAS HAPPENED AT LEAST 8 TIMES THAT I HAVE WITNESSED. 5 OF THE TIMES I KNOW THE COMMERCIAL OPERATOR FILED THE FLT PLAN AND THE OTHER 3 OCCURRED BEFORE I IDENTED THAT THIS IS A RECURRING PROB. THERE ARE 3 ISSUES THAT I SEE AND THEY ARE ALWAYS THE SAME. 1) THE PLT IS REQUESTING THE GATEWAY 4 DEP; BUT IT IS NOT BEING ENTERED INTO THE FLT PLAN. INSTEAD; THERE IS A STATEMENT PLACED IN THE REMARKS SECTION OF THE FLT PLAN STATING 'REQUEST GATEWY4.' I HAVE SEEN ICAO FORMATTED FLT PLANS THAT CONTAIN THE GATEWAY 4 DEP IN THE FLT PLAN RTE. I DO NOT KNOW WHO FILED THESE CORRECTLY. 2) THE FLT PLAN RTE ALWAYS HAS BLV AS THE FIRST FIX E OF SUS IN THE FLT PLAN. TODAY'S CLRNC WAS 'KSUS..BLV..ROD..KCVG.' BLV IS AN ARPT AND NOT A NAV FIX. ACFT ENRTE SHOULD BE NAVING TO NAV FIXES AND NOT TO ARPTS ALONG THE RTE. 3) THE FLT PLAN INDICATES FULL RTE CLRNC; BUT THIS INDICATION IS BURIED IN THE REMARKS. TODAY'S REMARKS WERE: 'ACFT X IRMK/FRC0REQUEST GATEWY4.' THIS HAS ALMOST AND MOST CERTAINLY WILL CAUSE ERRORS IN THE NATL AIRSPACE SYS. IT IS EXTREMELY EASY TO OVERLOOK THE FRC WHEN IT IS BURIED IN THE REMARKS. IF THE FLT PLAN HAD BEEN ENTERED PROPERLY; A FULL RTE CLRNC WOULD NOT BE NECESSARY.

Data retrieved from NASA's ASRS site as of May 2009 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	795720
Time
Date	200807
Place
Locale Reference	airport : sus.airport
State Reference	MO
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : corporate
Make Model Name	Learjet 60
Operating Under FAR Part	Part 91
Flight Phase	ground : parked
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : clearance delivery
Experience	controller non radar : 17
ASRS Report	795720
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	FAA Company
Primary Problem	FAA

Sus local controller voiced concern regard the newly adopted ICAO format for filing flight plan information; alleging SID is not included in route but in remarks.