37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1229694 |
Time | |
Date | 201501 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | BOS.Airport |
State Reference | MA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR ROBUC ONE |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 25000 |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance |
Narrative:
I flew flight from ZZZ to bos as pilot monitoring. We were expecting to fly the ROBUC1 to runway 27. While on bos center we were told to descend to FL230. Subsequently; we switched to bos center (freq 134.0) where we were told to 'go direct krann and to fly the runway 27 transition'. Familiar with the arrival; we had not heard this phraseology. We misunderstood and thought we were cleared to descend and fly the transition and started to descend to be over krann between 11;000 ft and 13;000 ft and above 8;000 ft at ansly etc. As hard arrival published altitudes (not expects).center observed us descending and had us level off at 21;000 ft. I inquired as to what 'cleared to fly the transition to runway 27' means; did it mean we could fly the track and not the altitudes or the speeds? The response was that he didn't know and the controllers were waiting for training before they could give a 'descend via' clearance; that all he could say was 'cleared to fly the transition' and that the pilots were supposed to know what that meant. Once I realized ATC had not actually said 'descend via' I realized we should have questioned the clearance before descending. As soon as we switched to approach we were given 'descend via the 27 transition'. Landed without incident. We expected to be cleared to 'descend via' the approach then when we got different wording we 'assumed' that we could fly the SID as published but obviously that wasn't what was expected. Listening more closely and question when any other words from the controller are heard. This is new to all of us; controllers and pilots alike.
Original NASA ASRS Text
Title: Pilots flying into BOS were told to fly the Runway 27 transition and they misunderstood and thought they also had descent clearance on the approach.
Narrative: I flew flight from ZZZ to BOS as Pilot Monitoring. We were expecting to fly the ROBUC1 to runway 27. While on BOS Center we were told to descend to FL230. Subsequently; we switched to BOS center (freq 134.0) where we were told to 'Go direct KRANN and to fly the RWY 27 transition'. Familiar with the arrival; we had not heard this phraseology. We misunderstood and thought we were cleared to descend and fly the transition and started to descend to be over KRANN between 11;000 FT and 13;000 FT and above 8;000 FT at ANSLY etc. as hard arrival published altitudes (not expects).Center observed us descending and had us level off at 21;000 FT. I inquired as to what 'cleared to fly the transition to RWY 27' means; did it mean we could fly the track and not the altitudes or the speeds? The response was that he didn't know and the controllers were waiting for training before they could give a 'Descend via' clearance; that all he could say was 'Cleared to fly the transition' and that the pilots were supposed to know what that meant. Once I realized ATC had not actually said 'Descend via' I realized we should have questioned the clearance before descending. As soon as we switched to approach we were given 'descend via the 27 transition'. Landed without incident. We expected to be cleared to 'Descend via' the approach then when we got different wording we 'Assumed' that we could fly the SID as published but obviously that wasn't what was expected. Listening more closely and question when any other words from the controller are heard. This is new to all of us; controllers and pilots alike.
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.