I had this happen twice today- I replicated it the second time and made sure the flightplan in FSX and in RC were correct.

 

I have never had this issue before- I flew the Feel There ERJ-175 KDTW to KJFK. I am pretty experienced with the ERJ series and have flown this jet numerous times before using RC with no issues.

 

This is my route...generated by FSX, simple, no SIDS or STARS...

 

CRL--->COHOW--->SURLY--->HAMIT--->JHWBFD1--->HOXIE--->SFK04--->STENT--->MAGIO--->LVZ--->JENNO--->HARTY--->STW--->LGA--->JFK.

 

At about 25 nm into COHOW, over Lake Erie, I am handed off to Toronto Centre.

 

This controller tells me I am off course, and asks me to turn to a heading of 275 degrees (west), esentially sending me in the complete opposite direction.

 

What on earth? LOL. Very frustrating. I searched and couldn't find anyone else with this issue.

 

Any ideas?

CRL is about 10 nm from DTW at 212 degrees. Leaving CRL to COHOW is 93 degrees.

 

Since CRL falls within the 30 nm departure zone of DTW, you are by RC required to do your own navigation crossing CRL and then setting yourself up for 212 heading to COHOW.

 

That's a pretty tight turn at CRL. You have to cross CRL within 1 nm to get waypoint credit. Did you see CRL pop off the status section of the RC window as you crossed it? If you did not receive credit RC would send you back to cross it.

 

The ERJ bank limitation and your crossing speed might cause too much of a turn anticipation causing CRL not to be crossed within the 1 nm limit and maybe you did not get credit. To get around this without going back choose the extended menu (9) by default and request direct next checkpoint selecting probably COHOW. When granted go to COHOW from your present position to dirrect to it without returning to your original planned path.

 

Here's a real world route traveled today by Delta:

 

KDTW MOONN5 JHW J70 STENT J70 MAGIO J70 LVZ LENDY6 KJFK

 

Name Latitude Longitude Distance from origin Distance from destination Type

KDTW 42.2124167 -83.3533889 0 508 Origin Airport

MOONN 42.3693333 -82.4519722 47 465 Reporting Point

MOONN 42.3693333 -82.4519722 47 465 Reporting Point

BROKK 42.3313889 -81.5819444 91 421 Reporting Point

BEWEL 42.2898611 -80.7619167 133 379 Reporting Point

JHW 42.1886111 -79.1213056 217 297 VOR-DME (NAVAID)

JHW 42.1886075 -79.1213050 217 297 VOR-DME (NAVAID)

HOXIE 41.8650111 -77.8526056 284 228 Reporting Point

DMACK 41.7857583 -77.5519222 300 212 Reporting Point

STENT 41.6790472 -77.1527556 321 190 Reporting Point

STENT 41.6790472 -77.1527556 321 190 Reporting Point

MAGIO 41.5273833 -76.5964944 351 159 Reporting Point

MAGIO 41.5273833 -76.5964944 351 159 Reporting Point

LVZ 41.2728025 -75.6894678 401 109 VOR-TAC (NAVAID)

LVZ 41.2728056 -75.6894722 401 109 VOR-TAC (NAVAID)

JENNO 41.1529167 -75.3314167 421 89 Reporting Point

HARTY 41.0711944 -75.0898889 434 75 Reporting Point

MUGZY 41.0301389 -74.9693611 441 68 Reporting Point

STW 40.9958333 -74.8690278 447 62 VOR-DME (NAVAID)

LENDY 40.9148333 -74.1352500 485 27 Reporting Point

LGA 40.7837222 -73.8686111 501 11 VOR-DME (NAVAID)

KJFK 40.6397511 -73.7789256 508 0 Destination Airport

 

This is from flightaware.com DAL2561 this morning.

 

Here's a plot of your plan in FSBuild:

 

https://www.dropbox.com/s/k8evxiq285qe5o0/singularity%20kdtw%20kjfk%20plotted%20via%20FSBuild.jpg?dl=0

 

and Delta 2561:

 

https://www.dropbox.com/s/5uvyjvhmdmeppeg/Delta2561%20KDTW%20KJFK.jpg?dl=0

Well, I knew it would be something stupid that I overlooked. 

 

What you are saying makes sense and I am 100% sure that it is the issue now that you point it out. I don't recall hearing the "ding" and I should have been paying more attention. 

 

Thanks for your help, I sincerely appreciate you taking the time to post that response.