RANT-ON! GTN750 question RANT-OFF!

FlySince9

En-Route
Joined
Mar 7, 2011
Messages
3,151
Location
Huntersville, NC
Display Name

Display name:
Jerry
Our club installed one last September... I love the thing, really... Buuut...

Last weekend I was trying to build a flightplan with a Private Airport in the routing... GTN became stupid... "What the He!! is NC21?" it asked..."do you want to add new waypoint?
No, I don't! Dammit! I want this one!


So, What's up with this? I know you can change runway length to 0 in setup and it will include all runways regardless of length, in "NEAREST" ForeFlight includes these, every freak'n nav app on the market includes these... And they didn't cost $20K!!!
 
Most of the IFR navigators do not have private strips in the database. I have to put the several I use in as user waypoints.
 
EGPWS boxes don't like it when you land on strip that isn't in the database.
 
I don't really blame the box, it's Jepps cheap azz, they are the ones who are putting out the databases, and the garmin only knows what's in that database.

But I agree it's BS, for what Jepp charges to regurgitate free gov data, it's disgusting, and frankly would be unacceptable by most any other industry, car databases, free Google maps, etc, but because Jepp doesn't get a ton of people bitching them out about it, they just keep with the same. It's too bad there isn't another contender in the database update market.
 
I don't know the exact criteria for inclusion, but I notice that NC21 does not have an airport ID listed on the VFR sectional, while the similar sized nearby 28A does have the ID on the sectional and is included. So I wonder if that's related.
 
It doesn't have an AF/D entry. I wonder if that's the reason??
Doubtful. If it has an identifier, there's an airport master record and that means the electronic data jepp or garmin got has it. They just chose to exclude it from the database.
 
Doubtful. If it has an identifier, there's an airport master record and that means the electronic data jepp or garmin got has it. They just chose to exclude it from the database.

As I noted above, the FAA does not include this airport's ID on the current VFR sectional. I wonder if Garmin considers it a liability issue, esp. given the recent episode in Long Island where someone tried to land engine-out IMC on a built-over runway? On the Garmin, if the airport exists in the DB it would show up in the Nearest listing (assuming it's in the "wide open" mode).
 
As I noted above, the FAA does not include this airport's ID on the current VFR sectional. I wonder if Garmin considers it a liability issue, esp. given the recent episode in Long Island where someone tried to land engine-out IMC on a built-over runway? On the Garmin, if the airport exists in the DB it would show up in the Nearest listing (assuming it's in the "wide open" mode).
Again doubtful. Neither the AF/D nor the SECTIONAL is a primary source. The VFR navigators like the 496... all have the private strips. The IFR units 430... do not. Don't know about the VFR panel units (probably don't either). The LONG ISLAND case was ATC misdirecting someone to a closed strip. There's a difference between CLOSED and PRIVATE. The only reason the closed strips remain charted is for "visual navigational" reasons. The closed fields are removed from the airport master records. They wouldn't show up in databases derived from them.
 
I don't know the exact criteria for inclusion, but I notice that NC21 does not have an airport ID listed on the VFR sectional, while the similar sized nearby 28A does have the ID on the sectional and is included. So I wonder if that's related.

Hmm. NC21, four characters. 28A, three characters. Wonder if there is some significance to that.
 
By and large the STATE+2 are private airports where the LETTER(corresponding to ARTCC area) + 2 belong to public use, but there are exceptions both ways. Since the databases do appear to have the full ICAO versions (K or P + three letters), I doubt it's got anything to do with identifier length.
 
Okay... I guess the next time I'll just use the Graphical update feature and "rubberband" the dam thing into the flight plan... RANT OFF... thanks guys...
 
NC21 was properly found in ForeFlight and it had runway data.
 
It isn't the panel mount, it is the Jepp Database installed in it :cool: I suspect Jepp would claim it is a database size issue. That airport (obviously) does not have an IFR approach, and there are thousands of airports like it, so adding them would increase the size of the database on the card, and add costs for them to maintain that info.
Now that doesn't mean I agree, just guessing on their reasoning.
Foreflight is for both VFR and IFR, so they have no excuse for not including it.
 
Back
Top