Ce-680 flight crew reported ATC indentified a track deviation when the FMC performed a fly-by rather...

Narrative:

ATC expects flyover and the FMC reads flyby (SID depicts flyby)we were issued an obscure clearance out of san jose which read sjc 2 departure to the moony intersection back to the sjc VOR and onward to the bmrng intersection. The moony intersection is not a fly over way point so the FMS turned back to the north towards the sjc VOR well short of the way point. This brought the attention of the controller who explained to us that we were off course turning 20 miles north of this 180 degree turn as the FMS is designed to do since it is not a fly over waypoint. He advised us this is a nav deviation and he would be filing paper work on it and advised us to do the same. I called norcal once we were en route and had a constructive conversation about what went wrong. [The nct representative] explained that this has happened before and I explained why the FMS turned when it did. [My first officer] pulled up an article explaining how the FMC/FMS works which depicts a very similar scenario. I asked [the nct representative] if he had seen this publication. Whether he has seen it or not; I did suggest that a track needs to be published depicting a fly over waypoint for the moony intersection or realistically a point closer to the VOR than the moony intersection. By the time we turn downwind on this departure we were at 7500 feet well clear of inbound traffic as well as the terrain.

Original NASA ASRS Text

Title: CE-680 flight crew reported ATC indentified a track deviation when the FMC performed a fly-by rather than a fly-over departing SJC.

Narrative: ATC expects flyover and the FMC reads flyby (SID depicts flyby)We were issued an obscure clearance out of San Jose which read SJC 2 departure to the MOONY intersection back to the SJC VOR and onward to the BMRNG intersection. The MOONY intersection is not a fly over way point so the FMS turned back to the north towards the SJC VOR well short of the way point. This brought the attention of the Controller who explained to us that we were off course turning 20 miles north of this 180 degree turn as the FMS is designed to do since it is not a fly over waypoint. He advised us this is a nav deviation and he would be filing paper work on it and advised us to do the same. I called NorCal once we were en route and had a constructive conversation about what went wrong. [The NCT representative] explained that this has happened before and I explained why the FMS turned when it did. [My First Officer] pulled up an article explaining how the FMC/FMS works which depicts a very similar scenario. I asked [the NCT representative] if he had seen this publication. Whether he has seen it or not; I did suggest that a track needs to be published depicting a fly over waypoint for the MOONY intersection or realistically a point closer to the VOR than the MOONY intersection. By the time we turn downwind on this departure we were at 7500 feet well clear of inbound traffic as well as the terrain.

Data retrieved from NASA's ASRS site 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	1603918
Time
Date	201812
Place
Locale Reference	NCT.TRACON
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Citation Latitude (C680A)
Operating Under FAR Part	Part 135
Flight Phase	Climb
Person 1
Function	Captain Pilot Not Flying
Qualification	Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP)
Person 2
Function	Pilot Flying First Officer
Qualification	Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types

Ce-680 flight crew reported ATC indentified a track deviation when the FMC performed a fly-by rather than a fly-over departing sjc.