37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 905246 |
Time | |
Date | 201008 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | HTO.Airport |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation Excel (C560XL) |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb Initial Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
[We were] departing hto on runway 28; climbing to initial altitude of 2;000' MSL. ATC clearance route of flight: hto V139 wacky dct …. After 400' AGL; pilot flying engaged FMS LNAV. At approximately 1;500' MSL; because of the large turn (almost a course reversal) onto V139; northbound; the FMS sequenced hto VOR behind the aircraft approximately 2.5 NM before overflight of hto VOR. Pilot flying turned the aircraft north following the flight director. Within 1 minute; new york departure queried if we had passed hto VOR. I responded that we had indeed passed hto VOR. New york departure informed us that we needed to check our equipment; because we had turned north 4 miles prior to reaching hto VOR and we should know that we had to cross hto VOR before turning north. Our ATC clearance did not specify hto VOR as an overfly point. Hto VOR is 3.5 DME from der 28; and we had reached 1;500' MSL before initiating the turn; so I estimate we had turned approximately 2.5 DME from hto VOR.with an initial waypoint and course reversal so close; perhaps hto should be defined as a 'flyover' waypoint; or we should query ATC if they actually want a 'flyover' waypoint; or they should publish a SID directing a 'flyover' waypoint.
Original NASA ASRS Text
Title: The flight crew of a CE560XLS and ATC disagreed as to the proper flight track required to comply with an enroute clearance from HTO VOR to WACKY intersection after departing KHTO toward the VOR.
Narrative: [We were] departing HTO on Runway 28; climbing to initial altitude of 2;000' MSL. ATC Clearance Route of Flight: HTO V139 WACKY DCT …. After 400' AGL; pilot flying engaged FMS LNAV. At approximately 1;500' MSL; because of the large turn (almost a course reversal) onto V139; northbound; the FMS sequenced HTO VOR behind the aircraft approximately 2.5 NM before overflight of HTO VOR. Pilot flying turned the aircraft north following the flight director. Within 1 minute; New York Departure queried if we had passed HTO VOR. I responded that we had indeed passed HTO VOR. New York Departure informed us that we needed to check our equipment; because we had turned north 4 miles prior to reaching HTO VOR and we should know that we had to cross HTO VOR before turning north. Our ATC clearance did not specify HTO VOR as an OVERFLY point. HTO VOR is 3.5 DME from DER 28; and we had reached 1;500' MSL before initiating the turn; so I estimate we had turned approximately 2.5 DME from HTO VOR.With an initial waypoint and course reversal so close; perhaps HTO should be defined as a 'flyover' waypoint; or we should query ATC if they actually want a 'flyover' waypoint; or they should publish a SID directing a 'flyover' waypoint.
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.