Phoenix Children's Hospital
Phoenix, Arizona

FAA NFDC Information Effective 56-day cycle 01/05/2017 - 3/2/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:AZ99
Lat/Lng: 33.4792222222, -112.042111111
33-28-45.2000N, 112-02-31.6000W
Estimated by OWNER on 08/22/2003
Elevation: 1175 feet Estimated by OWNER on 08/22/2003
Magnetic Variation: [10E (2017)]
Sectional: PHOENIX
From City: 1nm NE of Phoenix


Use: Private
Airspace Analysis: CONDITIONAL
Provided Private VFR. Sponsor Shall Ensure Obstruction Free Routes of Ingress/Egress.
Ownership: Privately owned
Activation: 08/2003
Control Tower: no
ARTCC: Albuquerque Center (ZAB)
FSS: Prescott FSS (PRC)
Wind Indicator: Lighted
Lights: for Perimeter Lights, Flood Lights and Rotating Beacon Call 602-933-5500.
Beacon: Phone Req
Clear-Green-Yellow (Heliport)
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Phoenix Children's Hospital
1919 East Thomas Rd
Phoenix, Az 85016
Manager: Craig M Crosby
1919 East Thomas Rd
Phoenix, Az 85016


Runways: H1

Runway H1

Length: 40 feet
Width: 40 feet
Surface: Porland Cement Concrete
Runway Lights Edge Intensity: Perimeter
Flood Lights Available.
Remarks: Helipad Located Atop Parking Garage, 54 Ft AGL.

Runway H2

Length: 46 feet
by Owner on 05/05/2008
Width: 46 feet
Surface: Roof, Top
Runway Lights Edge Intensity: Perimeter
Peri and Field Lights.
Remarks: H2 is Used As the Primary Helipad.



Additional Remarks

This information is current as of the date at the top of the page. These pages are valid for all US airports, based on information from FAA National Flight Data Center. Weather information is provided based on AvnWx Data Sources. NOTAM information is from FAA's NAIMES data portal.

As with most information on this website, this page is generated based on FAA data, with automatic translations done via computer. You can also directly read the A/FD via the green icon link at the top of the page, which is the FAA text, and sometimes provides a different translation of codes. Please email me (using link at top-right of this page) if you see information which is confusing, misleading, or wrong....Or have suggestions for additions/changes.

Comments from the user community are clearly noted as such this page, are for informational purposes only, may be wrong and/or out-of-date, and must not be used as a sole source for critical decision making. See Privacy Policy and Conditions of Use.