Port Lavaca, 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:10XA (One-Zero-Xray-Alpha)
Lat/Lng: 28.6799472222, -96.6608972222
28-40-47.8100N, 096-39-39.2300W
Estimated by OWNER on 09/25/2009
Elevation: 30 feet Estimated by OWNER on 09/25/2009
Magnetic Variation: [3E (2017)]
Sectional: HOUSTON
From City: 3nm S of Port Lavaca


Use: Private
Airspace Analysis: CONDITIONAL
Provided Owners of Proposed Airport and Calhoun County Airport (7Ts5) Enter Into An Opnl Loa.
Ownership: Privately owned
Activation: 04/2011
Attended: All year Every day DAWN-DUSK (local)
Control Tower: no
ARTCC: Houston (ZHU) Houston Center (ZHU)
FSS: Montgomery County FSS (CXO)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 2
Multi Engine GA: 1
Total: 3

Annual Operations

For year ending: 06/01/2010
Total: 0


Owner: John a. Sterling
1012 Bauer Rd
Port Lavaca, Tx 77979
Manager: John a. Sterling
Cell: 361-935-6006
1012 Bauer Rd
Port Lavaca, Tx 77979


Runways: 14/32

Runway 14/32

Length: 2300 feet
by Owner on 09/25/2009
Width: 20 feet
Surface: Asphalt / Bituminous Concrete
End 14 End 32
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach



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.