37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 919047 |
Time | |
Date | 201011 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | TEB.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Cessna Citation Sovereign (C680) |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 60 Flight Crew Total 4200 Flight Crew Type 200 |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I was the PIC on the ILS 6 approach into teb in a CE680. It was night and VMC conditions prevailed. During the approach briefing neither of us initially caught and/or remembered the mandatory 1;500 ft crossing altitude at dandy intersection. We had loaded the approach into the FMS for vectors to the final approach course with torby as the only intersection (dandy and vings were not loaded). At about 16 miles from dandy we were told to intercept the localizer on a heading of 090 and 2;000 ft. We had some problems with localizer reception at that distance and had to switch to FMS navigation until we could get a reliable signal. Once established on the localizer at about 13 miles from dandy (now still about 6.8 miles from vings) approach cleared us; 'you are 13 miles from dandy; maintain 2;000 until established; cleared for the ILS6'. The [first officer] read back the clearance and it was then with the mention of dandy; that my memory about the mandatory altitude was sparked. I remembered the crossing restriction and realized that with only torby in the FMS and no brief about the DME distances that identified dandy and vings; that we had lost situational awareness about when we could and when we were supposed to descend to 1;500 ft. I prompted the sic to pull up the approach and re-enter it into the FMS off of sbj (so that vings and dandy were in the flight plan) and to set 1;500 ft in the altitude alerter. The approach never was loaded correctly so I reached down and entered dandy intersection into the flight plan manually; but I didn't enter vings. I now had RNAV distance info from dandy. In the confusion I descended early; at my estimation about 2-3 miles outside of vings; to 1;500 ft. I know this because during the descent I finally regained situation awareness and noted that we were 8.5 miles from dandy; which is still 2.3 miles from vings. From my recollection we either crossed vings while still in the descent from 2;000-1;500; maybe around 1;800 ft or we might have crossed it already level at 1;500 ft. Either way we were not 'established' and descended too early at the improper distance. ATC made no mention of the mistake.
Original NASA ASRS Text
Title: A CE680 Captain on the TEB ILS 6 reported that his verbal approach brief was incomplete. In addition the FMS was not fully loaded so the crew did not remember the approach's crossing restrictions and began the descent to 1;500 FT early.
Narrative: I was the PIC on the ILS 6 approach into TEB in a CE680. It was night and VMC conditions prevailed. During the approach briefing neither of us initially caught and/or remembered the mandatory 1;500 FT crossing altitude at DANDY Intersection. We had loaded the approach into the FMS for vectors to the final approach course with TORBY as the only intersection (DANDY and VINGS were not loaded). At about 16 miles from DANDY we were told to intercept the localizer on a heading of 090 and 2;000 FT. We had some problems with localizer reception at that distance and had to switch to FMS navigation until we could get a reliable signal. Once established on the localizer at about 13 miles from DANDY (now still about 6.8 miles from VINGS) Approach cleared us; 'You are 13 miles from DANDY; maintain 2;000 until established; cleared for the ILS6'. The [F/O] read back the clearance and it was then with the mention of DANDY; that my memory about the mandatory altitude was sparked. I remembered the crossing restriction and realized that with only TORBY in the FMS and no brief about the DME distances that identified DANDY and VINGS; that we had lost situational awareness about when we could and when we were supposed to descend to 1;500 FT. I prompted the SIC to pull up the approach and re-enter it into the FMS off of SBJ (so that VINGS and DANDY were in the flight plan) and to set 1;500 FT in the altitude alerter. The approach never was loaded correctly so I reached down and entered DANDY Intersection into the flight plan manually; but I didn't enter VINGS. I now had RNAV distance info from DANDY. In the confusion I descended early; at my estimation about 2-3 miles outside of VINGS; to 1;500 FT. I know this because during the descent I finally regained situation awareness and noted that we were 8.5 miles from DANDY; which is still 2.3 miles from VINGS. From my recollection we either crossed VINGS while still in the descent from 2;000-1;500; maybe around 1;800 FT OR we might have crossed it already level at 1;500 FT. Either way we were not 'established' and descended too early at the improper distance. ATC made no mention of the mistake.
Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.