Regional Jet CL65; Undifferentiated or Other Model
Flight Crew Air Transport Pilot (ATP)
Training / Qualification; Confusion; Human-Machine Interface
Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Company Policy; Human Factors; Aircraft; Chart Or Publication
I'm writing this with the hopes of getting clarification regarding GPS Approach Procedures. When loading a GPS Approach from the FMS database; sometimes certain fixes do not load with the approach. We are allowed to [manually] add these fixes [unless] they fall between 2.0 NM outside the FAF to the MAP; or we can identify these fixes using Along Track Distance if it is displayed as such on the chart. For example; when loading the RNAV GPS Y 18C at CLT; HAGUL does not load with the approach. Since HAGUL is 3.2 NM from the FAF; we can add it to the legs page. The problem arises when doing an approach such as the RNAV GPS Y 36C at CLT. NIVSE does not load with the approach. We can't add it to the legs page because it is 1.6 NM from the FAF. The mileage depicted on the profile view is NOT depicted as Along Track Distance. Therefore; one would deduce that we cannot legally shoot this approach because we have no legal means to identify NIVSE. We come across this issue frequently in the training department. We can't seem to get a firm answer regarding the legality of shooting this approach.
A CL65 Captain reported that company SOP will not allow manual entry of waypoints on RNAV approaches unless they are located more than 2.0 NM outside the FAF. He cites CLT RNAV GPS Y Runway 36C as an example. Waypoint NIVSE is only 1.6 NM from the FAF (GLASI) and cannot; per SOP; be manually entered when flying the approach. The procedure requires that NIVSE be crossed at 3;000 MSL and GLASI at 2;500; thus; NIVSE must be displayed and its restrictions complied with.