<< >> NASA ASRS Report 545433, April 2002

Departure clearance issued to C550 from ZOA through oak FSS departing mry after tower closure results in aircraft departing from other than assigned IFR departure procedure.

Attributes
ACN	545433
Time
Date	200204
Day	Sat
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : mry.airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zoa.artcc
Operator	general aviation : corporate
Make Model Name	Citation II S2/Bravo
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff
Route In Use	departure sid : munso 2
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zoa.artcc
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Plan	VFR
Person 1
Affiliation	government : faa
Function	controller : radar
Qualification	pilot : private
Experience	controller radar : 16 controller time certified in position1 : 16 flight time total : 700
ASRS Report	545433
Person 2
Affiliation	government : faa
Function	other personnel
Events
Anomaly	non adherence : published procedure non adherence : far non adherence : clearance other anomaly other other spatial deviation
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Airport Environmental Factor Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was working sector 12 at ZOA. Monterey approach closed for the night. I relayed a clearance to aircraft X through oak FSS. I issued the munso 2 departure procedure (which is for a takeoff on runway 28L). I had some traffic near sns (east of mry) that I needed to keep the aircraft X from. Aircraft X took off on runway 10R. When I asked why, he said because that was the preferred noise abatement runway. The traffic at sna was VFR in the meantime, so the takeoff direction did not matter at that time. Although I did not ask which runway aircraft X was going to use, I thought the pilot would advise if he was unable to comply with my clearance. Recently, a directive came down telling us that if a departure procedure is available for an airport, it shall be issued. This incident makes me wonder why bother!

Related reports:

• Small aircraft GA depart vgt no flight plan and when contact...
• Iad TRACON had an aircraft fly through departure airspace wi...
• Small aircraft climbs through assigned altitude on departure...
• MD80 flight crew had a rather busy and complicated departure...
• ARTCC radar controller points out an aircraft that needs to ...

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

Original NASA ASRS Text

Title: DEP CLRNC ISSUED TO C550 FROM ZOA THROUGH OAK FSS DEPARTING MRY AFTER TWR CLOSURE RESULTS IN ACFT DEPARTING FROM OTHER THAN ASSIGNED IFR DEP PROC.

Narrative: I WAS WORKING SECTOR 12 AT ZOA. MONTEREY APCH CLOSED FOR THE NIGHT. I RELAYED A CLRNC TO ACFT X THROUGH OAK FSS. I ISSUED THE MUNSO 2 DEP PROC (WHICH IS FOR A TKOF ON RWY 28L). I HAD SOME TFC NEAR SNS (E OF MRY) THAT I NEEDED TO KEEP THE ACFT X FROM. ACFT X TOOK OFF ON RWY 10R. WHEN I ASKED WHY, HE SAID BECAUSE THAT WAS THE PREFERRED NOISE ABATEMENT RWY. THE TFC AT SNA WAS VFR IN THE MEANTIME, SO THE TKOF DIRECTION DID NOT MATTER AT THAT TIME. ALTHOUGH I DID NOT ASK WHICH RWY ACFT X WAS GOING TO USE, I THOUGHT THE PLT WOULD ADVISE IF HE WAS UNABLE TO COMPLY WITH MY CLRNC. RECENTLY, A DIRECTIVE CAME DOWN TELLING US THAT IF A DEP PROC IS AVAILABLE FOR AN ARPT, IT SHALL BE ISSUED. THIS INCIDENT MAKES ME WONDER WHY BOTHER!

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.