2XA2
Airport
Knape
Danbury, Texas

FAA NFDC Information Effective 56-day cycle 04/03/2014 - 5/29/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:2XA2
Lat/Lng: 29.2204222222, -95.3108805556
29-13-13.5200N, 095-18-39.1700W
Estimated by OWNER on 10/23/2006
Elevation: 20 feet Estimated by OWNER on 10/23/2006
Magnetic Variation: [3E (2014)]
Sectional: HOUSTON
From City: 2nm WNW of Danbury

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Right Traffic Runway 04, Clear 20:1 Approaches.
Ownership: Privately owned
Activation: 10/2006
Attended: Continuous
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: James Knape
Po Box 938
Danbury, Tx 77534
979-922-8484
Manager: James Knape
Po Box 938
Danbury, Tx 77534
979-922-8484

Runways

Runways: 04/22

Runway 04/22

Length: 2400 feet
by Owner on 10/23/2006
Width: 100 feet
Surface: Grass / Sod
End 04 End 22
Right Hand Pattern: Yes  
Objects:   Powerline
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height:   25' AGL
Object Distance:   800' Along centerline

Procedures

NOTAMs

Additional Remarks

300 Ft Antenna 1.5 NM WNW.

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.