Data Base cycle during a trip....

RLVoumard

Filing Flight Plan
Joined
Dec 13, 2013
Messages
25
Display Name
RLV
Just curious .......I will be overnight on a IFR trip ..the 430W nav data base will be cycling .

I have only 1 data card ...how do most people handle this ? Take the laptop and re program before departure would be my method ..

Thanks in Advance
 
Technically, without the current database, you are not legal for IFR. I don't even think the upcoming cycle is technically legal if you aren't in that cycle date range yet. I would be interested in hearing some more knowledgable people weigh in on this.
 
Technically, without the current database, you are not legal for IFR.
IFR enroute is allowed with an expired database, if the pilot validates the waypoints he plans to use to ensure there are no changes.
IFR approaches are not allowed, to my recollection.
So it would be legal to fly GPS to the destination and do a non-GPS approach.
 
For the GTN750, you can pre-load the upcoming database, while the current database is still in use, then on the update day, it automatically fills. But, that's with the SD card, I don't know if your older 430 card has room for that.
 
Just curious .......I will be overnight on a IFR trip ..the 430W nav data base will be cycling .

I have only 1 data card ...how do most people handle this ? Take the laptop and re program before departure would be my method ..

Thanks in Advance
This is why I paid money for the second card years ago. But yeah, take the laptop and program upon expiration in the hotel room - or wherever you are staying.
 
For the GTN750, you can pre-load the upcoming database, while the current database is still in use, then on the update day, it automatically fills. But, that's with the SD card, I don't know if your older 430 card has room for that.
430W erases all data and writes the new data.
 
Yeah, the 430 was always crap from a usability standard. The 480 (aka CNS-80) held two copies of the database (on an industry-standard card) for just this reason.
 
IFR enroute is allowed with an expired database, if the pilot validates the waypoints he plans to use to ensure there are no changes.
IFR approaches are not allowed, to my recollection.
So it would be legal to fly GPS to the destination and do a non-GPS approach.

That is how I understand it as well.
 
IFR enroute is allowed with an expired database, if the pilot validates the waypoints he plans to use to ensure there are no changes.
IFR approaches are not allowed, to my recollection.
So it would be legal to fly GPS to the destination and do a non-GPS approach.
Of course, the most accurate answer is in the Limitations section of your AFM/Supplement.
 
IFR enroute is allowed with an expired database, if the pilot validates the waypoints he plans to use to ensure there are no changes.
IFR approaches are not allowed, to my recollection.
So it would be legal to fly GPS to the destination and do a non-GPS approach.

It depends on the AFMS version. All allow "enroute navigation" using your method of validating waypoints. Some versions of the GNS430W AFMS permit flying an instrument approach with an out of date database as long as the approach data is verified to be current. This is easier to accomplish than validating individual waypoints because you can compare the procedure amendment date on a current chart with the effective date of the database, and if the chart procedure amendment date is on or before the effective date of the out of date database, then the approach may be flown. This wording is used up until version 3.30 of the GNS AFMS and permits using an out of date database for instrument approaches if the conditions specified are complied with.

2.3 Navigation Database

b. GPS instrument approaches using the 400W Series units are prohibited,
unless the 400W Series unit’s approach data is verified by the pilot or
crew to be current. Instrument approaches must be accomplished in
accordance with an approved instrument approach procedure that is
loaded from the 400W Series unit database.

Later versions of the AFMS had the following limitation, the last version 5.40 reads as follows:

2.4 Navigation database
GPS/SBAS based IFR enroute, oceanic, and terminal navigation is prohibited
unless the flight crew verifies and uses a valid, compatible, and current
navigation database or verifies each waypoint for accuracy by reference to
current approved data
That seems to limit approaches only if the database is current. However, there is also this statement in the same section:

If the navigation database cycle will change during flight, the flight crew must
ensure the accuracy of navigation data, including suitability of navigation
facilities used to define the routes and procedures for flight. If an amended chart
affecting navigation data is published for the procedure, the database must not
be used to conduct the procedure.

The GTN Xi series, most current version has updated the limitation wording and now doesn't distinguish between enroute and procedures:

2.5 Navigation Database
GPS/SBAS based IFR operations are prohibited unless the flight crew verifies
and uses a valid, compatible, and current navigation database or verifies each
waypoint for accuracy by reference to current approved data.
 
Last edited:
This is why I have two data cards...
 
Back
Top