Briggs, Texas

FAA NFDC Information Effective 56-day cycle 09/14/2017 - 11/9/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:TX23
Lat/Lng: 30.8562930556, -97.9458530556
30-51-22.6550N, 097-56-45.0710W
Elevation: 1150 feet Estimated
Magnetic Variation: 07E, (1985), [4E (2017)]
Sectional: SAN ANTONIO
From City: 2nm SW of Briggs


Use: Private
Airspace Analysis: CONDITIONAL
Provided All Operations are Conducted in Accordance W/Operational Letter of Agreement Provided Asw-600 on 01/09/88.
Ownership: Privately owned
Activation: 08/1988
Attended: All year Sat-Sun 0800-2000 (local)
Control Tower: no
ARTCC: Fort Worth (ZFW) Fort Worth Center (ZFW)
FSS: San Angelo FSS (SJT)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 1
Gliders: 15
Total: 16

Annual Operations

Total: 0


Owner: Fault Line Flyers, Inc
1804 Oakridge Dr
Round Rock, Tx 78681
Manager: William Brinkman
1804 Oakridge Dr
Round Rock, Tx 78681


Runways: 16/34

Runway 16/34

Length: 4500 feet
Width: 300 feet
Surface: Grass / Sod
End 16 End 34
Right Hand Pattern:   Yes
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach



Additional Remarks

All Traffic Pattern Operations to be Conducted East of the Field.
Glider Operations on & in Vicinity of Gliderport.

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.