All entries must be numerical, in the form dd/mm/yyyy. Dates must be entered in UTC.
It is not necessary to enter leading zeros, so 01/01/2004 and 1/1/2004 are both acceptable.
2-digit years will be accepted, and converted to 4-digit years in the range 1970-2069. Dates outside this range must be entered as 4 digits.
If you enter just a day and month (dd/mm), the current year will be assumed.
If you enter just a day (dd), the current month and year will be assumed.
Pressing the up or down cursor key will increment or decrement the date by one day.
Where dates are required in the flying and simulator logs, there is a calendar icon next to the date entry box. Clicking this will show a pop-up calendar: Select the correct month using the < and > buttons, and the correct year using the << and >> buttons, then click the correct date. Clicking 'today' will jump to the current month and year. Today's date is highlighted in red. Clicking 'close' will close the calendar without making any changes.

All entries must be in the form hh:mm. Times must be entered in UTC.
It is not necessary to enter leading zeros, so 06:30 and 6:30 are both acceptable.
For speed of typing, it is acceptable to omit the ':', so '630' will be understood as '06:30'.
The exception to this rule is when entering previous flying hours, where the ':' must be used to avoid ambiguity (between 10:00 and 1000:00, for example), and whole numbers will be treated as whole hours (630 will be interpreted at 630:00).

In the simulator log and when entering previous experience, durations are entered rather than times.
Durations must be entered in the format chosen in the user preferences for 'display hours totals as'.
Regardless of the format selected, a whole number of hours can be entered without any minutes or decimals.

Any alphanumeric registration will be accepted.
Entries are not case-sensitive, so g-aaaa, G-AAAA and G-aAaA will be understood to be the same.
When adding flights, it is acceptable to omit the hyphen, so gaaaa and g-aaaa will both be recognised.
When adding aircraft to the aircraft database, the full registration (g-aaaa) must be entered as this is how it will be displayed.
When aircraft are added to the database, registrations are converted to upper case automatically.

The recommended format is the 4-letter ICAO code (e.g. EGLL for London Heathrow).
3-letter IATA codes will also be understood (e.g. LHR for London Heathrow).
It is possible to enter a name or part name (so long as it is not 3 or 4 characters long) and the program will attempt to match it to an entry in the database. It is possible that this will return more that one match (e.g. 'London' will match Heathrow and Gatwick, among others). In this case, the first match found will be assumed, and a warning message will pop up. If the incorrect airport has been assumed, it should be re-entered using more detail, or preferably the ICAO/IATA code.
Entries are not case-sensitive for matching purposes.
3- and 4-letter codes are converted to upper case once verified. Airport names are stored as entered.