I've been wondering for a while now, why many, if not most of the RNAV SIDs do not have they're transitions coded as transitions in the navdata updates. Here's an example from the latest navdata, 1002...
This is the COKEM4 departure out of KATL
COKEM4 HRSHL --- 8L,8R COKEM4 KLEGG --- 8L,8R COKEM4 NAVVY --- 8L,8R COKEM4 LIDAS --- 9L,9R COKEM4 ERWIN --- 9L,9R COKEM4 SHELE --- 10 COKEM4 HEDEG --- 10 COKEM4 LUVIE --- 10 COKEM4 ESSEY --- 9L,9R,10 COKEM4 MPASS --- 26L,26R COKEM4 ZELAN --- 26L,26R COKEM4 FUTBL --- 27L,27R COKEM4 WESEK --- 27L,27R COKEM4 WLSON --- 28 COKEM4 SOTRE --- 28 COKEM4 WODEB --- 27L,27R,28 COKEM4 COKEM COKEM4 CARPT
Refering the the chart, CARPT is a transition but in the above data is not coded as such. If a flight plan is coded as COKEM4 COKEM... as I have found many times on flightaware the result is a route where the flight will proceed to CARPT and then back to COKEM before flying the rest of the route. If the SID is coded as follows...
COKEM4 HRSHL --- 8L,8R COKEM4 KLEGG --- 8L,8R COKEM4 NAVVY --- 8L,8R COKEM4 LIDAS --- 9L,9R COKEM4 ERWIN --- 9L,9R COKEM4 SHELE --- 10 COKEM4 HEDEG --- 10 COKEM4 LUVIE --- 10 COKEM4 ESSEY --- 9L,9R,10 COKEM4 MPASS --- 26L,26R COKEM4 ZELAN --- 26L,26R COKEM4 FUTBL --- 27L,27R COKEM4 WESEK --- 27L,27R COKEM4 WLSON --- 28 COKEM4 SOTRE --- 28 COKEM4 WODEB --- 27L,27R,28 COKEM4 COKEM COKEM4.CARPT CARPT
Then everything works as expected. These missing transition codings seem to only exist for RNAV SIDs. Non-RNAV SIDs seem to all be coded correctly. I've noticed this problem for KATL, KCLT, KDFW, and KCVG but I'm guessing it may occure at any airport with RNAV SIDs. I hope this has made sense. Thanks.
_________________ Dave Paige
PPL ASEL Instrument
|