Buffalo Chips Airpark
Joshua, Texas

FAA NFDC Information Effective 56-day cycle 06/22/2017 - 8/17/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:TE45
Lat/Lng: 32.4698616667, -97.4652977778
32-28-11.5020N, 097-27-55.0720W
Elevation: 960 feet Estimated
Magnetic Variation: 07E, (1985), [4E (2017)]
From City: 4nm NE of Joshua


Use: Private
Airspace Analysis: CONDITIONAL
Provided Thrs are Displaced to Provide a Clear Approach Surface of 20:1 Over Any Obstns in the Approach Areas.
Ownership: Privately owned
Activation: 03/1988
Control Tower: no
ARTCC: Fort Worth Center (ZFW)
FSS: Fort Worth FSS (FTW)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 8
Multi Engine GA: 2
Jet GA: 3
Helicopter GA: 18
Total: 31

Annual Operations

Total: 0


Owner: Alan Sparks
Box 1456
Joshua, Tx 76058
Manager: Alan Sparks
Box 1456
Joshua, Tx 76058


Runways: 17/35

Runway 17/35

Length: 5400 feet
Width: 100 feet
Surface: Grass / Sod
End 17 End 35
Displaced Threshold Distance: 500' 500'
Objects: Powerlines Powerlines
Object Marking: Marked and Lighted Marked and Lighted
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 25' AGL 25' AGL
Object Distance: 100' Along centerline 100' Along centerline



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.