Technical Review Q400 F2011 - 2

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

APU Louvers:

The whole airBaltic Q400 fleet is now fitted with APU Louvers for winter operations. These louvers
allow de-/anti-icing fluid to run over the APU intake and are a requirement for keeping the APU
operating (if required) during fluid application (OM-B 2.5.1.8). When louvers are installed a placard
to this effect is installed on the APU Control Panel on the Overhead Panel, see image below. An
image of the louvers installation is also provided. In a transition period because of our north/south
operation, please be aware of the +21°C maximum ambient operating temperature. Additionally pay
attention to the minimum operating temperature of -35°C (OM-B 1.7.2).

Landing Gear Alternate Release Door:

We’ve had one incident where the landing gear would not retract after GEAR-UP selection on
departure. The QRH non-normal checklist dealing with this situation is “ALL LANDING GEAR FAIL TO
RETRACT”.

One likely cause why this occurs is inappropriate closing of the Landing Gear Alternate Release Door.
The Landing Gear Alternate Release Door is used on the ground by maintenance staff to open the
landing gear doors to gain access during daily checks etc. The image below on the left shows an
actual event how the Landing Gear Alternate Release Handle was found stowed when the L/G
Alternate Doors/Inhibit SW item on the BEFORE START checklist was challenged. In this position the
Landing Gear Alternate Release Door may not be sufficiently closed, which actuates a bypass valve
to isolates the #2 hydraulic system, and consequently the gear from retracting.

To avoid incidents like this from happening, ensure that the Release Handle is properly stowed
(parallel to wings / left-right, see illustration below to the right), and the Release Door is properly
closed.
 

FORE - AFT, WRONG

LEFT - RIGHT, CORRECT

Multiple Identifiers in FMS:

The navigation database contains a number of non-unique or “duplicate” identifiers, that


is, multiple items using the same identifier. These may include enroute and terminal
waypoints, intersections, VORs, VOR/DMEs, NDBs, TACANs, airports, localizers and
ILSs.

If there are two or more items with the same identifier, multiple pages will be displayed
next to the identifier in X/Y format. The value 1/ 1, if displayed, indicates the item is
unique, such as KTUS 1/ 1. If the database contains an identifier used more than once,
such as “R” which is used 31 times in the navigation database, it will be shown as
R 1/ 31. The items are ranked in order of distance from present position or distance from
a preceding waypoint in a flight plan or route, where 1/ 31 is closest and 31/ 31 is
furthest, see illustration below.

Navigate between pages on the Control Display Unit (CDU) to view remaining
items on the list by pressing <NEXT> or <PREV>.
VORs and NDBs often occur with the same identifier at the same or nearly the same
location. If the NDB is selected, using <LIST><AIRWAYS> will not show any airways
based on the VOR because the NDB is not part of the airway structure, and vice versa.
Airports and enroute waypoints sometimes occur with the same identifier at the same
location. Attempting to link an approach to the flight plan using <MENU><ARRIVE>
based on an enroute waypoint may cause incorrect courses to be displayed on the
CDU.

In summary, the Navigation Database contains numerous duplicate identifiers. The flight crew has
the ultimate responsibility of properly identifying their selected item to ensure it is the one
they intended to use.

You might also like