Chris Hofer Landing Strip
Tea, South Dakota

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:3SD4
Lat/Lng: 43.4651430556, -96.862725
43-27-54.5150N, 096-51-45.8100W
Estimated by FAA on 06/02/2004
Elevation: 1515 feet Estimated by STATE on 03/13/2013
Magnetic Variation: [3E (2017)]
Sectional: OMAHA
From City: 2nm NW of Tea


Use: Private
Airspace Analysis: CONDITIONAL
Provided Traffic Pattern is W of Runway to Avoid Overlap with Maro Skei Airport, Clear Obstacle Free Zone, Clear Runway Safety Area, and Clear 20:1 Approaches.
Ownership: Privately owned
Activation: 06/2004
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Huron FSS (HON)
Wind Indicator: Lighted
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Chris Hofer
46730 271St St
Tea, Sd 57064
Manager: Chris Hofer
46730 271St St
Tea, Sd 57064


Runways: 16/34

Runway 16/34

Length: 2300 feet
by State on 03/13/2013
Width: 120 feet
Surface: Grass / Sod
End 16 End 34
True Alignment: 164, (161 Magnetic) 344, (341 Magnetic)
Right Hand Pattern: Yes  
Elevation at End: 1515.0' MSL 1500.0' MSL
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach



Additional Remarks

All Traffic Remain W of Airport.

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.