 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier flight crew reported on the arrival into mtpp they were cleared for the RNAV 10 via the savar 1C STAR; during the descent when the crew reported a waypoint with an altitude; the controller stated he had not issue a descent. Crew requested an altitude assignment and rest of the approach was uneventful.
| Attributes | |
| ACN | 1408641 |
| Time | |
| Date | 201612 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | MTEG.ARTCC |
| State Reference | FO |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR SAVAR 1C |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
When checking in with mtpp control on frequency 124.5; we reported level at FL290 and gave estimate for joses intersection. Mtpp control gave current local weather; landing runway; and reported opposite direction traffic at FL280 and told us to report over joses 'expect no delays'. We eventually spotted opposite direction traffic; reported traffic in site and advised clear of traffic. Other aircraft reported us in site and also reported clear. Mtpp asked our position and we reported over joses intersection. Mtpp then advised us we were cleared for RNAV 10 via the savar 1C arrival and to report next waypoint; 'medon'. We acknowledged the clearance and advised leaving FL290. Passing medon; we reported crossing with current altitude. We were in VNAV on the normal descent profile at approximately FL210. Mtpp then stated he had not issued a descent. This was a surprise to us as we had reported leaving FL290; he had made sure we were clear of opposite direction traffic; and then gave arrival routing and runway. Had we not begun descent and made the requested call over medon at FL290; our rate of descent would have been excessive. Instead of arguing the clearance received; I asked for an altitude assignment. Mtpp said to continue to 10;000 ft. The remainder of approach was uneventful. We flew this same arrival the next day and when reporting over joses we received similar clearance; but were advised to maintain 9;000 ft.I have flown this arrival many times and the clearance is slightly different based on other arrivals and departures in this non-radar environment. The concern with traffic and the request that both aircraft report clear of opposite direction traffic near joses intersection combined with 'expect no delays' was our clue we were #1 on arrival. In the future I will confirm the altitude cleared to since our 'standard' phraseology may not be standard here; i.e.; descend via.
Original NASA ASRS Text
Title: Air carrier flight crew reported on the arrival into MTPP they were cleared for the RNAV 10 via the SAVAR 1C STAR; during the descent when the crew reported a waypoint with an altitude; the Controller stated he had not issue a descent. Crew requested an altitude assignment and rest of the approach was uneventful.
Narrative: When checking in with MTPP control on frequency 124.5; we reported level at FL290 and gave estimate for JOSES intersection. MTPP control gave current local weather; landing runway; and reported opposite direction traffic at FL280 and told us to report over JOSES 'expect no delays'. We eventually spotted opposite direction traffic; reported traffic in site and advised clear of traffic. Other aircraft reported us in site and also reported clear. MTPP asked our position and we reported over JOSES intersection. MTPP then advised us we were cleared for RNAV 10 via the SAVAR 1C arrival and to report next waypoint; 'MEDON'. We acknowledged the clearance and advised leaving FL290. Passing MEDON; we reported crossing with current altitude. We were in VNAV on the normal descent profile at approximately FL210. MTPP then stated he had not issued a descent. This was a surprise to us as we had reported leaving FL290; he had made sure we were clear of opposite direction traffic; and then gave arrival routing and runway. Had we not begun descent and made the requested call over MEDON at FL290; our rate of descent would have been excessive. Instead of arguing the clearance received; I asked for an altitude assignment. MTPP said to continue to 10;000 ft. The remainder of approach was uneventful. We flew this same arrival the next day and when reporting over JOSES we received similar clearance; but were advised to maintain 9;000 ft.I have flown this arrival many times and the clearance is slightly different based on other arrivals and departures in this non-radar environment. The concern with traffic and the request that both aircraft report clear of opposite direction traffic near JOSES intersection combined with 'expect no delays' was our clue we were #1 on arrival. In the future I will confirm the altitude cleared to since our 'standard' phraseology may not be standard here; i.e.; descend via.
Data retrieved from NASA's ASRS site 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.