|
|
>
|
|
Two (or more) Aircraft with the same Registration
|
|
|
This covers cases such as the following:
- You fly or have flown different aircraft with the same registration
- You fly the same aircraft under multiple operators (airlines, companies, etc) and want your log to reflect this at the aircraft level (as opposed to simply filling in a different 'Company' field for each flight)
- You fly the same aircraft in significantly different configurations (with floats on or in landplane mode, for example) and want your log to reflect this
The way to handle these issues (and other similar ones) is all the same.
There are two approaches we can follow. We encourage you to set up both on a full size device on SafelogWeb.com rather than on a mobile device or client app as working directly on SafelogWeb.com will give you the most direct access to the latest and most capable tools and UI for something like this.
Approach 1: Give them Different Registrations in Safelog
There are no fixed rules for this, but here are some examples:
- G-BAAA (your current aircraft) vs G-BAAA-OLD (the aircraft the reg used to be on)
- VH-ABC-QANTAS vs VH-ABC-QEXPRESS
- N123AB-LAND vs N-123AB-SEA
The upside to this approach is that it's quite simple - just go into SafelogWeb.com, click on "Aircraft", and add/edit these as you like. The downside to this is that the "registrations" can get a bit wide and also tht, strictly speaking, they are not registrations. We used dashes above for the 'other part' such as "-OLD" but there's no particular reason you have to. The other downside to this approach is that if you import your data from an external source such as your airline source, you have to make sure the registrations actually match though there is something you can do to mitigate this: go to SafelogWeb.com ... Import/Export ... Automatic Importer and then look for a button to manage aircraft cache near the top. There, you can set it so that if the system sees VH-ABC from your import source that it will match to VH-ABC-QANTAS for example.
Approach 2: Same Registration in Safelog, Set Old aircraft to "Inactive" where possible.
This is a "cleaner" approach but requires slightly more care. This approach is simply this: log into SafelogWeb.com, click on 'Aircraft.' and create multiple records with the same registration. There's nothing stopping you from doing this, though you may encounter warnings if you do. If you're actively only flying one version of a given registration, as will normally be the case, edit the 'inactive' records to be 'inactive.' The advantages of this include that import features will look at active (that is to say, non-inactive) records first for a given registration*.
Obviously, when you select an aircraft for a given flight, you'll need to make sure that you select the correct aircraft. This requires slightly more care if you have multiple of the same registration. Also, on certain reports it might not be immediately obvious which aircraft is being referred to. However, for most people this works fine.
* There is some logic in place for when the import source includes both a registration and an aircraft type. However, we urge you to be very cautious with this as aircraft types are often sent in various ways and it is not uncommon for the system to potentially not be sure enough that the two are the 'same' to use this as part of its matching logic and it will err on the side of caution. It is far better to just mark old aircraft as 'inactive.' It is also important to be aware of your aircraft import cache status when you have multiple aircraft with the same registration - a fixed cache status could be forcing incoming data into an 'old' registration until you fix it, regardless of 'active' status. Go to SafelogWeb.com ... Import/Export ... Automatic Importer and then Mange Cache or Aircraft Cache at the top to manage this.
|
|
|
|
|
|
|
