Navigation completely ignoring a turn.

That's two out of many, many turns.

If you can, provide the address of that.

I had to go back and look that location up. It happens more than these two times, but not terribly frequently. Until recently I thought it to be random until I had a similar course two weekends in a row and it occured in the same location. I can't recall exact locations of other places its happened. This is the only other I'm 100% sure of. It's not a huge issue but in the heat of a race, blowing past a turn going down hill and having to grind back up is a bit frustrating.

The other known location is the intersection of Lost Trail and Koala Ave. in Guthrie County Iowa. I see now that that one maintains staying on Lost Trail(haha) by turning right(headed south/west) and straight would be Koala Ave. So it is possible that is the reason.

In some (many?) cases, there's some sort explanation for these kinds of issues. People might not remember where issues happened but, often, they do.

My position is that, if navigation is important, having the map displayed is almost necessary. I often know about turns before they would be announced. And, for whatever reason, one blows a turn, it's fairly easy to see it when looking at the map. 

There can be places where it would be reasonable to expect a notification (like splits at a Y) but you won't because of how the device works. Not announcing the Bierman intersection doesn't make sense (I'm surprised it was an issue).

------------------------------------------

I see 200th Street (at the north) and 215th Street (at the south). I don't see Lost Trail.

https://www.google.com/maps/search/+Koala+Ave.+in+Guthrie+County+Iowa/@41.707573,-94.556711,3488m/data=!3m1!1e3?hl=en&authuser=0

goo.gl/.../BsCNXtciaTUjdcdY6

Yea, I just wish I could display more than 2 data fields on the mapscreen, then I'd never deviate from the map page.

Also, if you blow a turn that wasn't notified, the unit does promptly tell you that you are off course.

You might try the "map dashboard" custom datafield. I use it on my 1030+ (which has a much bigger screen). Err, you have a 1040. Mapdashboard will work great on that.

https://apps.garmin.com/en-US/apps/8633c044-afff-4834-b71f-9f10113b5276

There are a few versions of this (one that lets you have six fields).

I don't see an issue there either.

I tried that CIQ data field and it would work perfectly for me, but it lacks Intensity Factor or Normalized Power(I can do with one or the other of these)