Sandy, you should tell the Committe that they should demand comprehensively detailed lists of both.
"LISTS" would be the "ONLY" way Sandy.
Producing "lists", from the databases, is a "SIMPLE" task, for the SQL heads in IT, one that the CASA could not legally "fudge".
Perhaps the Committee should ask for the list of the operators, broken down by AOC type, by category, by initial issue date, and by current expiry / or renewal date. Those lists should also include hours flown per line, for each one of the last 20 years.
Similarly, the Committee should ask for the list of all pilots, broken down by licence type, by category, by initial issue date, and by current medical expiry / or renewal date, and / or recency expiry / renewal date, including hours flown per pilot, for each one of the last 20 years.
Only with these details "readily to hand", could the true health of the industry be gauged.
The committe should also replace the "ask" with "demand" - and the date for production should be tomorrow - not some time next century "on notice" - but tomorrow.
You see, a competent SQL head could write the QUERY in two minutes flat - and computers are "FAST".
"LISTS" would be the "ONLY" way Sandy.
Producing "lists", from the databases, is a "SIMPLE" task, for the SQL heads in IT, one that the CASA could not legally "fudge".
Perhaps the Committee should ask for the list of the operators, broken down by AOC type, by category, by initial issue date, and by current expiry / or renewal date. Those lists should also include hours flown per line, for each one of the last 20 years.
Similarly, the Committee should ask for the list of all pilots, broken down by licence type, by category, by initial issue date, and by current medical expiry / or renewal date, and / or recency expiry / renewal date, including hours flown per pilot, for each one of the last 20 years.
Only with these details "readily to hand", could the true health of the industry be gauged.
The committe should also replace the "ask" with "demand" - and the date for production should be tomorrow - not some time next century "on notice" - but tomorrow.
You see, a competent SQL head could write the QUERY in two minutes flat - and computers are "FAST".