| 1G4
Airport
|
Grand Canyon West
|
|
Peach Springs, Arizona
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | 1G4 (One-Golf-Four) |
| Lat/Lng: |
35.9861125, -113.816922222
35-59-10.0050N, 113-49-00.9200W
Estimated by FAA-EST on 07/08/2011
|
| Elevation: |
4813 feet
Surveyed
by OWNER
on 08/27/2012
|
| Magnetic Variation: |
14E,
(1985),
[12E (2013)]
|
| Sectional: |
LAS VEGAS
|
| From City: |
60nm
NW of Peach Springs
|
| Use: |
Open to the public
|
| Airspace Analysis: |
CONDITIONAL
Provided Operations Conducted During VFR Conditions; Sponsor Ensure All Operations Adhere to the Communications & Coordination Requirements for VFR Traffic Operating Within & Between the Boundaries of Class E and Class B Airspace.
|
| Ownership: |
Publicly owned
|
| Activation: |
10/1988
|
| Attended: |
All year Every day Daylight hours
|
| Control Tower: |
no
|
| ARTCC: |
Los Angeles Center
(ZLA)
|
| FSS: |
Prescott FSS
(PRC)
|
| NOTAMs and Weather: |
PRC
NOTAM-D service at airport
|
| Wind Indicator: |
Unlighted
|
| Segmented Circle: |
yes
|
| Lights: |
Activate REIL Runway 17/35; MIRL Runway 17/35 - CTAF.
|
| Beacon: |
Sunset-Sunrise (local time)
Clear-Green (Lighted Land Airport)
|
| Landing Fee: |
yes
|
| ARFF: |
III A S 12/2005
Index a
|
| CTAF: |
122.900
|
| Weather: |
AWOS-3PT
119.425
|
| Airframe Repair: |
None
|
| Powerplant Repair: |
None
|
| Bottled Oxygen: |
None
|
| Bulk Oxygen: |
None
|
| Transient Storage: |
Tie-Down
|
|
|
| For year ending: |
08/01/2012
|
| AirTaxi: |
130000
|
| Non-local GA: |
300
|
| Total: |
130300
|
|
| Owner: |
the Hualapai Indian Tribe
P.O. Box 359
Peach Springs, Az 86434
928-769-2419
Airport Manager Ext 216
|
| Manager: |
Stephan Degan
Po Box 359
Peach Springs, Az 86434
928-769-2419
Ext 216 or 702-494-9631 After 7:00 Pm.
|
|
Runway 17/35
| Length: |
5000 feet
by Owner on 06/29/2011
|
| Width: |
75 feet
|
| Surface: |
Asphalt / Bituminous Concrete, Good Condition
|
| Surface Treatment: |
Saw-cut or Plastic Grooved
|
| Weight Capacity: |
Single Wheel aircraft: 30,000 lbs
|
| Runway Lights Edge Intensity: |
Med Intensity
|
|
End 17 |
End 35 |
| Right Hand Pattern: |
Yes
|
|
| Runway Markings: |
Nonprecision Instrument,
Good Condition
|
Nonprecision Instrument,
Good Condition
|
| Gradient: |
1.1 Up
|
|
| Elevation at End: |
4758.2' MSL
|
4813.4' MSL
|
| Threshold Crossing Glide Path Height: |
39' AGL
|
38' AGL
|
| Visual Glide Path Angle: |
3.00°
|
3.00°
|
| Visual Glide Slope Indicator: |
4-light PAPI on left side of runway
|
4-light PAPI on left side of runway
|
| Runway End Identifer Lights (REIL): |
Yes
|
Yes
|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
| • | (E111-1) Due to the Proximity of This Airport to Special Federal Aviation Regulation - Sfar 50-2 - Grand Canyon National Park Special Flight Rules Area; Particular Attention Shall be Given to the Specific Regulation in the Sfar That Apply to All Aircraft Operations Below 14500 Ft MSL. |
| • | Due to High Commerical Fixed Wing and Helicopter Traffic Volume No Practice Touch and Go Operations. |
| • | Recommend Using Runway 35 for Departures and Runway 17 for Landings. |
| • | Use Extreme Care Due to Large Volume of High-Speed Fixed Wing & Rotary Wing Traffic in & Around Vicinity of the Airport. |
| • | Transient Aircraft Must Park at South End of Apron. |
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.