Unusually distant IAF

I am interested in what the flight plan waypoint was immediately before the gap in route at the top of the screenshot. Based on the sidebar in the screenshot, there were many waypoints in the flight plan between the active waypoint (MONTY) and the flight plan portion displayed in the screenshot.

I was able to replicate a similar scenario in the IFD Trainer for AviOS 10.2.3.1. I think there are possibly two issues going on here:

1. To me, it seems that the flight plan waypoint immediately prior to the gap in route may have actually been a waypoint whose IFD database lat/lon was in fact 7816 NM from MMBSA and 7828 NM from YMMB. That is why it would be highly useful to see what the waypoint immediately before the gap in route actually was. There numerous reasons an erroneous waypoint could end up in the flight plan than include both human factors as well as possible database errors.
   
   
2. While not specifically demonstrated in this screenshot; in researching this scenario I did come across what seems to be an anomaly with the mini flight plan format like shown.
   
   Before the gap in route was created by inserting the RNAV 35R approach to YMMB, the flight mini and standard flight plan format would have shown the distance between the YMMB and the waypoint prior to it (7828 NM in this example). The anomaly appears to occur when the gap in route is created with the selection of an approach (RNAV 35R at YMMB); the mini flight plan format appears to lock the before gap insertion leg distance to the approach airport. This distance is locked as long as the gap remains and prior to the missed approach (at which point the locked distance is replaced by ---). At this point, any changes made in the flight plan on the non-approach side of the gap in route will not alter the locked airport distance (7828 NM in this example) shown at the approach airport in the mini flight plan format.
   
   In other words, even had this pilot determined the waypoint just prior to the gap was erroneous; changing or clearing that waypoint from the flight plan after the gap was created would not have changed the fixed 7828 NM distance shown at YMMB unless the gap was also cleared by any number of methods.
   
   Showing the standard flight plan format or cursor highlighting the mini flight plan format approach airport to expand it to standard format with the gap in route will cause the approach airport distance to indicate active direct distance to the airport. In the mini flight plan format, as soon as the flight plan cursor is moved off the approach airport, the locked leg distance will return as the waypoint reverts back to the mini flight plan format.
   
   This mini flight plan format anomaly appears to also be present in the IFD Trainer for AviOS 10.3.0.2.