Flight plan validation[PDF]
- 1 Introduction
- 2 Flight plan validation: procedure
- 3 Basic mistakes in a flight plan
- 4 Flight plan validation: where and when?
- 5 See also
- 6 Reference
- 7 Author
The flight plan check is very important on initial contact to be sure that the pilot has not made mistakes in it, will respect current valid routes and will respect local regulations in function of the selected flight rules.
Flight plan validation: procedure
There are two options for a flight plan validation:
- First validation or simple verification of the flight strip available in IvAc
- Second validation or full flight plan verification by opening the ICAO format flight plan
Flight strip validation
The figure below shows a typical flight strip that any controller shall know and understand.
The basic checks of the flight strip are:
- Check of the departure and the arrival airfield ICAO code
- Check the alternate airfield compatible with arrival and departure
- Check the first cruise altitude selected in function of route restriction or semi-circular rules of levels
- Check aircraft type in function of type of flight rules selected or information given by the pilot
- Check the Flight rules of the flight in function of the route and altitude/flight level selected
- Check squawk code in function of transponder number given in the clearance
- Check route in function of departure airfield and arrival airfield and flight rules selected
- Check cruising speed estimated. This speed is the true air speed.
- Check off-block time when necessary
- Check Remarks area when necessary
Full flight plan validation
Editing a flight plan
But be advised that the FPL is a pilot´s responsibility; that’s why you may use this feature for training reasons only. If you wish an update of the flight plan in any other cases, you may advise the pilot – he has to change it.
Basic mistakes in a flight plan
Departure and arrival ICAO code
The controller shall pay attention to these fields for a departing aircraft. It is possible that pilots leave the last departure and destination airfields or other data saved from previous flights in their flight plans.
The controller shall pay attention to this field for a departing aircraft. It is possible that pilots leave the last alternate airfield or other data saved from previous flights in their flight plans.
Requested flight level or altitude
Sometimes the pilot doesn’t know the ICAO code of his aircraft or he forgets to update this field from a previous flight. If you detect a false aircraft, please tell the pilot to confirm the exact aircraft he uses.
Sometimes the pilot forgets to update this mandatory field. Typical mistakes are:
- Flight rules are IFR but flight plan is VFR
- Flight rules are VFR but flight plan is IFR
This speed must be the true air speed at the first requested flight level. Typical mistakes are:
- Speed given is the indicated airspeed and not the true air speed
- Speed unit is ‘K’ for km per hour and not ‘N’ for knots
Sometimes the pilot forgets to update the squawk/transponder code or sets a wrong squawk code. Air traffic controller can remind him to set the right code. The pilot must set the squawk code, if given, before any aircraft movement, even on the ground.
The controller shall also detect:
- Incorrect first en-route point not compatible with the standard departure charts
- Incorrect last en-route point not compatible with the arrival charts
- Not operational first en-route point in function of the route and departure airfield selected
- Not operational last en-route point in function of the route and destination airfield selected
- Incorrect en-route progressive points or route
Flight plan validation: where and when?
As first controller, you need to be sure that the flight plan is correct from your point of view by checking the different flight plan fields. ATC unit shall not ask flight plan modification during critical phases of flight (landing, take-off, final approach, emergency…).
The delivery controller communicates with IFR pilots only . He must display the flight plan and check it before the initial contact in order to check the flight plan.
When the flight plan is correct, the delivery controller can give the IFR departure clearance.
The ground controller shall follow the tasks of the delivery controller if this position is not opened.
The tower controller shall perform the tasks of the delivery and ground controllers if these positions are not opened.
===Approach (arrival and departure) controller The approach controllers shall follow the tower, ground and delivery of their controlled airfield only in their area of responsibility.
En-route controllers shall check incoming traffic flight plans of pilots coming:
- From outside his controlled area, especially when aircraft is coming from non-controlled areas
- From a departing airfield inside or below his controlled area
En-route controller shall also verify the adequate information given in the route in the flight plan and the current route availabilities and the usual known rules inside his airspace.
- VID 150259 - Creation
- VID 435695 - Wiki integration
DATE OF SUBMISSION
- 03:28, 14 May 2021
- This documentation is copyrighted as part of the intellectual property of the International Virtual Aviation Organisation.
- The content of this documentation is intended for aviation simulation only and must not be used for real aviation operations.