72TA
Airport
Pierce Field
Port O'Connor, Texas

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:72TA
Lat/Lng: 28.4586111111, -96.2919444444
28-27-31.0000N, 096-17-31.0000W
Estimated
Elevation: 5 feet Estimated
Magnetic Variation: 06E, (1990), [3E (2014)]
Sectional: HOUSTON
From City: 6nm W of Port O'Connor

Operations

Use: Private
Ownership: Privately owned
Activation: 11/1992
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: Montgomery County FSS (CXO)
Wind Indicator: Lighted
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Aaron C. Pierce
609 Bay Club Dr
Seabrook, Tx 77586
281-474-5852
Cell# 832-284-3971
Manager: Aaron C. Pierce
P.O. Box 259
Kemah, Tx 77565
281-474-5852

Runways

Runways: 06/24
18/36

Runway 06/24

Length: 6000 feet
Width: 75 feet
Surface: Porland Cement Concrete
End 06 End 24
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach

Runway 18/36

Length: 5000 feet
Width: 75 feet
Surface: Porland Cement Concrete
End 18 End 36
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach

Procedures

NOTAMs

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.