Hey folks -I'm trying to create a SID For the Baltimore-Washington Intl. Paleo Two departure. Before starting, I made sure to read the SID/STAR Syntax guide as well as reference the files of several other SID/STARs that I had installed. Seemed straightforward and easy enough, so I go to start coding out my first SID. The Paleo Two departure with Smyrna Transition is as follows:Fly runway heading until 3 DME from BAL VORTAC, then turn left heading 150. From over BAL VORTAC via BAL R-130 to PALEO INT, then via SIE VORTAC R-276 to SPEAK INT, then via ENO VORTAC R-235 to ENO VORTAC.Simple enough.. so here's what I put in my file.SID PALEO2.ENO RNW 28 KEEP HDG UNTIL 3 FROM NAVAID BAL HDG 150 INTERCEPT RADIAL 130 FROM BAL NAVAID PALEO INTERCEPT RADIAL 276 TO SIE NAVAID SPEAK INTERCEPT RADIAL 276 TO ENO NAVAID ENOWhen I load up KBWI as my departure airport in the FMC, I get the message "ERROR AT BAL, Line 9". No matter how I change stuff around, I always seem to get an error after the "KEEP HDG" point. Even if I take the "KEEP HDG" out and immediately turn to HDG 150, I still get an error. Looking at the syntax guide and the examples I have, I can't quite tell what exactly I'm doing wrong.. does anyone have any pointers? I managed to create a STAR for Rhode Island's TF Greene State, and that works without incident.. but this SID and its fellow transitions for BWI are making me pull my hair out.Many thanks in advance,Brian Schwark

Paleo3 is current.I fail to see how taking off 28 and turning to left to 150 will intercept the BAL R-130 (R-133 on my chart). It seems you will always be south of it. Isn't this a vector departure anyways in which they will clear you direct PALEO?The directions say "From over the BAL VORTAC...", which sounds like a right turn off 28 to overfly the field, but is that really done?Anyways, to your error message, I think you are missing a NAVAID between FROM and BAL.I'd be inclined to write this as:SID PALEO3.ENO RNW 28 KEEP HDG UNTIL 3 FROM NAVAID BAL NAVAID PALEO NAVAID SPEAK NAVAID ENOAll those intermediate radials seem unnecessary after PALEO as the direct track between waypoints are following the various radials. I'm guessing adding the intercepts would just add waypoints that clutter the map display.I have not tried this as I am not in front of FS.Lee Hetherington (KBED)

All I had access to was Paleo2 (from clearanceunlimited.com..), so I wasn't even aware of Paleo3. Like you said, though, adding all the intermediate waypoints was silly. The chart I have doesn't list it as being vectored to PALEO, and like you said, you're always south of the BAL R-130 if you turn to 150 at 3mi from BAL, which is why it's kinda weird to start off with. I think I'm dealing with an old or very screwed up chart! ;)At any rate, I tried what you suggested and it worked out just fine, which is odd seeing as I had tried a similar simplified syntax and still got an error. Perhaps I just don't have the magic touch!Thanks for your reply. :)-Brian

Actually, Departing off of runway 28, pilots turn to hdg 150 and contact Potomac Departure. Potomac then instructs the aircraft to intercept the SIE 276 radial and cleared to their ending transition fix as filed. The actual transmission would sound like;'Southwest 126 radar contact. Intercept the Sea Isle 276 radial, Atlantic City transition as filed, c/m FL230.'As far as the text in the SID, here goesSID PALEO3.ACY.28 RNW 28 KEEP HDG UNTIL 3 FROM NAVAID BAL HDG 150 INTERCEPT RADIAL 276 FROM NAVAID SIE NAVAID PALEO NAVAID SPEAK NAVAID DONIL NAVAID ACYHope that helps ya out.Andrew

Thanks Andrew.. I knew from sitting down at BWI and watching departures from 28 that there was a turn to 150 after takeoff, but then what they did from there was more or less a mystery to me. I need to get myself a scanner! ;)Much thanks,Brian