<< >> NASA ASRS Report 708140, August 2006

A falcon 50-ex departing phl deviated from clearance route because captain misread the pre departure clearance.

Attributes
ACN	708140
Time
Date	200608
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : phx.vortac
State Reference	PA
Altitude	msl single value : 5000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : phl.tracon
Operator	common carrier : air carrier
Make Model Name	Falcon 50
Operating Under FAR Part	Part 135
Navigation In Use	other
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 75 flight time total : 14800 flight time type : 3500
ASRS Report	708140
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	flight crew : returned to intended or assigned course
Supplementary
Problem Areas	Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

On departing phl on an IFR flight plan; we were told by the tower to contact phl departure control. Upon contacting them; they queried as to our heading. We replied that we were on runway heading after departing runway 27L. He said that we should be on a 255 degree heading. Before departure; we had looked at departure procedures and notice that it said to fly a 255 degree heading after takeoff if advised to. We had received our clearance via pre departure clearance. Upon looking at the clearance closer; it did say that we were cleared as filed; which was direct mxe VOR; but later in the pre departure clearance it said we were cleared via the phl 7 departure; which included a 255 degree heading after takeoff. We had received a pre departure clearance earlier at pit and it included the SID at the beginning of the pre departure clearance. I think that if the format for pre departure clearance's was standard; then we would not have missed the SID in the pre departure clearance at phl.

Related reports:

• A sabreliner departing mmsd deviated from the published SID ...
• A giv departing lfpb deviated from SID track because the fli...
• A CL65 departing dca deviated from assigned track because HS...
• A B737 departing sea deviated from the mountain 5 SID becaus...

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

Original NASA ASRS Text

Title: A FALCON 50-EX DEPARTING PHL DEVIATED FROM CLRNC RTE BECAUSE CAPT MISREAD THE PDC.

Narrative: ON DEPARTING PHL ON AN IFR FLT PLAN; WE WERE TOLD BY THE TWR TO CONTACT PHL DEP CTL. UPON CONTACTING THEM; THEY QUERIED AS TO OUR HDG. WE REPLIED THAT WE WERE ON RWY HDG AFTER DEPARTING RWY 27L. HE SAID THAT WE SHOULD BE ON A 255 DEG HDG. BEFORE DEP; WE HAD LOOKED AT DEP PROCS AND NOTICE THAT IT SAID TO FLY A 255 DEG HDG AFTER TKOF IF ADVISED TO. WE HAD RECEIVED OUR CLRNC VIA PDC. UPON LOOKING AT THE CLRNC CLOSER; IT DID SAY THAT WE WERE CLRED AS FILED; WHICH WAS DIRECT MXE VOR; BUT LATER IN THE PDC IT SAID WE WERE CLRED VIA THE PHL 7 DEP; WHICH INCLUDED A 255 DEG HDG AFTER TKOF. WE HAD RECEIVED A PDC EARLIER AT PIT AND IT INCLUDED THE SID AT THE BEGINNING OF THE PDC. I THINK THAT IF THE FORMAT FOR PDC'S WAS STANDARD; THEN WE WOULD NOT HAVE MISSED THE SID IN THE PDC AT PHL.

Data retrieved from NASA's ASRS site as of January 2009 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.