Today I built a flight from KIND to KBNA to simulate an IRL Southwest Airlines flight. When attempting to load the chart for KIND SID OOM5 on the iFly Max 8 EFB it was missing in the SID chart list. I thought maybe I was doing something wrong so when I finished the flight I opened Charts Cloud and selected KIND Charts/SID tabs and sure enough OOM5 is missing. I did find it under the Procedures/Departures tabs for KIND.
I also notice under Charts/SID there is a HOOSIER 5 SID that doesn’t appear under Procedures/Departures tab.
Yes, as far as I can tell, this is exactly what somiller is reporting:
OOM5: coded (navdata) but not charted
HOOSIER5: not coded (navdata) but charted (10-3A)
…which seemed to match what I was seeing from the FAACIFP file too.
Except, actually looking at the charts and its contents help
OOM is known as the Hoosier Bloomington VOR/DME and OOM5 is actually the HOOSIER FIVE departure, they are one and the same. It’s just charted under the descriptive name and coded under the 3-letter database name (and Morse identifier) of the VOR.
In Charts first search for KIND airport. Then select the charts icon then the SID tab - OOM5 is missing from the SID tab, and HOOSIER5 is there instead.
Except “instead” is not accurate. As we’ve determined above, they are one and the same, Hoosier Five is OOM5. Hoosier is the “full name” of the OOM VOR.
That’s fine, but it shows up as OOM5 in navdata. This is exactly why I was confused…I’ve never encounted something like this. It’s not that I’ve never seen discrepancies, it’s just that usually the differences at least relate - There is nothing about HOOSIER and OOM that would lead me to believe they are one-and-the-same.
I’m sure to the government it makes perfect sense.
You can’t set the full name for this procedure because it is simply too long. The standard ident length is max 5 characters. OOM is the VOR identity, 5 is the revision of this procedure, and HOOSIER is the full name for this VOR.
