37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 212189 |
Time | |
Date | 199206 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : mia |
State Reference | FL |
Altitude | msl bound lower : 19000 msl bound upper : 19000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zma |
Operator | common carrier : air carrier |
Make Model Name | Light Transport, Low Wing, 2 Turboprop Eng |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 4200 flight time type : 200 |
ASRS Report | 212189 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Events | |
Anomaly | other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified |
Resolutory Action | other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Air Traffic Incident | other |
Narrative:
Air carrier X flight was from tpa to mia, fl. We got a clearance to miami. After departure, I asked ZMA if I could go direct the snoke intersection (miami coiler 3 arrival). The snoke intersection is identifiable by 2 radials from coiler VOR and palm beach VOR. Our aircraft has the EFIS navigation package in it. So on our mfd (multi function display) we can have a visual picture of the intersection and navigation to it, with accuracy. Our canned flight plans, however, have us listed as an light transport/right not light transport/a. We do not have RNAV. ZMA cleared us direct the snoke at 19000 ft. Upon a frequency change to miami 132.35 the controller asked our heading to snoke. After I replied, she asked how we can accept direct to an intersection without RNAV. I explained, and asked her if we should not accept direct clrncs if we are not flight planned as an /a. She said no problem as long as we were not guessing on our heading, and suggested we change our canned flight plans to reflect the capability of a direct clearance.
Original NASA ASRS Text
Title: CTLR QUESTIONED ACR X ABOUT ACFT EQUIP AND ABILITY TO PROCEED DIRECT TO AN INTXN.
Narrative: ACR X FLT WAS FROM TPA TO MIA, FL. WE GOT A CLRNC TO MIAMI. AFTER DEP, I ASKED ZMA IF I COULD GO DIRECT THE SNOKE INTXN (MIAMI COILER 3 ARR). THE SNOKE INTXN IS IDENTIFIABLE BY 2 RADIALS FROM COILER VOR AND PALM BEACH VOR. OUR ACFT HAS THE EFIS NAV PACKAGE IN IT. SO ON OUR MFD (MULTI FUNCTION DISPLAY) WE CAN HAVE A VISUAL PICTURE OF THE INTXN AND NAV TO IT, WITH ACCURACY. OUR CANNED FLT PLANS, HOWEVER, HAVE US LISTED AS AN LTT/R NOT LTT/A. WE DO NOT HAVE RNAV. ZMA CLRED US DIRECT THE SNOKE AT 19000 FT. UPON A FREQ CHANGE TO MIAMI 132.35 THE CTLR ASKED OUR HDG TO SNOKE. AFTER I REPLIED, SHE ASKED HOW WE CAN ACCEPT DIRECT TO AN INTXN WITHOUT RNAV. I EXPLAINED, AND ASKED HER IF WE SHOULD NOT ACCEPT DIRECT CLRNCS IF WE ARE NOT FLT PLANNED AS AN /A. SHE SAID NO PROBLEM AS LONG AS WE WERE NOT GUESSING ON OUR HDG, AND SUGGESTED WE CHANGE OUR CANNED FLT PLANS TO REFLECT THE CAPABILITY OF A DIRECT CLRNC.
Data retrieved from NASA's ASRS site as of July 2007 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.