<< >> NASA ASRS Report 598933, November 2003

A320 flight crew does not 'over fly' a published fix on a departure from sjc, but lets the aircraft turn early and the controller issues an advisory that the fix should have been over flown.

Attributes
ACN	598933
Time
Date	200311
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	intersection : dyblo
State Reference	CA
Altitude	msl single value : 15000
Environment
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : nct.tracon
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude climbout : initial
Route In Use	departure sid : danville
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 240 flight time total : 7800 flight time type : 2700
ASRS Report	598933
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory
Consequence	faa : reviewed incident with flight crew other
Supplementary
Problem Areas	ATC Human Performance Aircraft Chart Or Publication Flight Crew Human Performance
Primary Problem	Ambiguous

Narrative:

On climb out of sjc on the SID DANVILLE2. The aircraft, A320 started the turn early, as it always does, before point dyblo to lin. Norcal departure told us we were turning too early and gave us a vector of 345 degrees to overfly point dyblo. ATC said we must overfly the point and that air carrier had been notified of this. Dyblo is not a circled waypoint nor is it in the NOTAMS to overfly. We complied with ATC directions and were later given direct lin. We contacted dispatch to see if they knew we were suppose to overfly dyblo. After consulting with air carrier's FAA rep, dispatch replied that dyblo is not an overfly point and we did the right thing. The captain and myself also notified the flight office upon arriving in ZZZ.

Related reports:

• While inbound on an arrival, an air carrier flight crew fail...
• Flight crew of a super MD80 slowed aircraft contrary to a pu...
• A corp small aircraft pilot asked to fly a published SID in ...
• ARTCC controller working an IFR aircraft in adjacent sector'...
• Phl controller issues published holding instructions at mazi...
• An air carrier L1011 off runway 25R at lax at the same time ...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: A320 FLT CREW DOES NOT 'OVER FLY' A PUBLISHED FIX ON A DEP FROM SJC, BUT LETS THE ACFT TURN EARLY AND THE CTLR ISSUES AN ADVISORY THAT THE FIX SHOULD HAVE BEEN OVER FLOWN.

Narrative: ON CLBOUT OF SJC ON THE SID DANVILLE2. THE ACFT, A320 STARTED THE TURN EARLY, AS IT ALWAYS DOES, BEFORE POINT DYBLO TO LIN. NORCAL DEP TOLD US WE WERE TURNING TOO EARLY AND GAVE US A VECTOR OF 345 DEGS TO OVERFLY POINT DYBLO. ATC SAID WE MUST OVERFLY THE POINT AND THAT ACR HAD BEEN NOTIFIED OF THIS. DYBLO IS NOT A CIRCLED WAYPOINT NOR IS IT IN THE NOTAMS TO OVERFLY. WE COMPLIED WITH ATC DIRECTIONS AND WERE LATER GIVEN DIRECT LIN. WE CONTACTED DISPATCH TO SEE IF THEY KNEW WE WERE SUPPOSE TO OVERFLY DYBLO. AFTER CONSULTING WITH ACR'S FAA REP, DISPATCH REPLIED THAT DYBLO IS NOT AN OVERFLY POINT AND WE DID THE RIGHT THING. THE CAPT AND MYSELF ALSO NOTIFIED THE FLT OFFICE UPON ARRIVING IN ZZZ.

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.