Ffz tower controller is informed by P50 that a corporate jet that departed ffz got below the MVA whi...

Attributes
ACN	833526
Time
Date	200904
Local Time Of Day	0601-1200
Place
Locale Reference	FFZ.Airport
State Reference	AZ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Light Transport
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	SID Obstacle DP
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Radar 8 Air Traffic Control Time Certified In Pos 1 (mon) 10 Air Traffic Control Time Certified In Pos 1 (yrs) 1
Events
Anomaly	Airspace Violation All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

A corporate jet departed ffz on the falcon field runway 4R obstacle departure procedure. P50 later reported to us that the aircraft got in position where it was below the MVA. As a controller here at ffz I've seen several problems resulting from this departure procedure. It is confusing; and outdated. Here are some of the problems with the departure procedure published on page C5 of us terminal procedures (south\west) vol 4. 1. The procedure utilizes the ffz NDB; many aircraft are no longer NDB equipped. 2. The procedure as published is a climbing left turn to 5000 ft; however by LOA we stop all departures at 3000 ft. 3. The second sentence in the procedure states 'for climb in visual conditions cross ffz NDB at or above 2300 then proceed via 220 bearing to pxr VORTAC R-143 southeast bound.' this does not specify a left or right turn back to the NDB. 4. Again; reference the second sentence in the procedure. In march 2009 the traffic pattern altitude was raised to 2400. Crossing the ffz NDB at or above 2300 creates a conflict with pattern traffic. 5. This procedure sends all aircraft southeast bound regardless of what direction they filed. Many pilots do not want to comply with the procedure. Proposed solution: write a new procedure that's more user friendly.

Original NASA ASRS Text

Title: FFZ Tower Controller is informed by P50 that a corporate jet that departed FFZ got below the MVA while attempting to comply with Runway 4L/R obstacle departure procedure. Controller believes the NDB departure procedure is confusing and outdated.

Narrative: A corporate jet departed FFZ on the Falcon Field Runway 4R obstacle departure procedure. P50 later reported to us that the aircraft got in position where it was below the MVA. As a Controller here at FFZ I've seen several problems resulting from this departure procedure. It is confusing; and outdated. Here are some of the problems with the departure procedure published on page C5 of U.S. Terminal Procedures (S\W) Vol 4. 1. The procedure utilizes the FFZ NDB; many aircraft are no longer NDB equipped. 2. The procedure as published is a climbing left turn to 5000 FT; however by LOA we stop all departures at 3000 FT. 3. The second sentence in the procedure states 'For climb in visual conditions cross FFZ NDB at or above 2300 then proceed via 220 bearing to PXR VORTAC R-143 southeast bound.' This does not specify a left or right turn back to the NDB. 4. Again; reference the second sentence in the procedure. In March 2009 the traffic pattern altitude was raised to 2400. Crossing the FFZ NDB at or above 2300 creates a conflict with pattern traffic. 5. This procedure sends all aircraft southeast bound regardless of what direction they filed. Many pilots do not want to comply with the procedure. Proposed solution: Write a new procedure that's more user friendly.

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.

Ffz tower controller is informed by P50 that a corporate jet that departed ffz got below the MVA while attempting to comply with runway 4L/right obstacle departure procedure. Controller believes the NDB departure procedure is confusing and outdated.