Browse
Search
Agenda - 08-01-1983
OrangeCountyNC
>
Board of County Commissioners
>
BOCC Agendas
>
1980's
>
1983
>
Agenda - 08-01-1983
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/24/2017 3:21:25 PM
Creation date
4/24/2017 10:05:27 AM
Metadata
Fields
Template:
BOCC
Date
8/1/1983
Meeting Type
Regular Meeting
Document Type
Agenda
Document Relationships
Minutes - 19830801
(Linked From)
Path:
\Board of County Commissioners\Minutes - Approved\1980's\1983
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
174
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
, . . <br /> "4 1- <br /> • :7/ :-;;?;":';- • 7r."7 4'r <br /> . , <br /> • <br /> Ai-7. Bruce Matthews, Airport Development Specialist of the NC. 021 <br /> Departmentlof Transportation, in a letter to Mr. Pollaty dated <br /> June 30, 1982, stated that developers should be required only <br /> to own or control the land lying under the Clear Zone portion <br /> of the Approach-Departure Zone (Exhibit B) . However, Mr.Matthews' <br /> earlier testimony in the form of a letter to Mr. Fred Luce, <br /> dated January 26, 1982 (Exhibit C) isin conflict with some <br /> portions of Mr. Matthews' letter. of June 30, 1982, In his <br /> letter of January 26, Mr: Matthews stated "We wish to emphasize <br /> that neither Federal nor State regulations require a private <br /> airport to meet F.A.A. design standards. However, failure to <br /> meet such standards could have an adverse effect on funding <br /> should the airport become publicly owned in the future. It could <br /> also adversely affect the potential for an instrument approach <br /> procedure, Which would probably be desirable early in the life of this <br /> airport. Onejlitemwhich is not shown on the plan is the approach zones <br /> for the runway. There would probably have to be some land interest <br /> J <br /> for areas within about 2000' of each end of the runway so that trees, <br /> powerlines, nd other obstructions could be removed, if necessary. " <br /> Thus, in this earlier letter Mr. Matthews states that an approach zone <br /> of about 2000 feet would have to be controlled by the airport owners <br /> whereas in ailater letter he changes his position and states that the <br /> developers would only have to control the clear zone (which would be <br /> 1200 feet from the end of the runway by F.A.A. standards (at a 20:1 <br /> slope), or 1100 feet by State standards. A letter from Mr. Willard <br /> C. Flentl, Jr., Director of the Division of Aviation of the N.C. Dept. <br /> of TransportItion, dated July 1 , 1982, (Exhibit D) seems to throw some <br /> light on the reasoning of the D.O.T officials. Mr. Plentl states: <br /> "We are Particularly concerned that the County may be going far beyond <br /> FAA standard in its requirements for private airports. As Bruce Matthews <br /> pointed out in his letter of June 28, FAA requires ownership or control <br /> of only the Cp.ear zone: Any controls beyond the clear zone normally <br /> takes the form of a height restriction zoning ordinance. Such an ordi- <br /> nance is clearly beyond the ability of a private citizen and should <br /> be a County responsibility.". Thus, the D.O.T seems to be taking the <br /> position thatIthe total approach zone should be controlled, but the <br /> airport develloper should be required to control only the clear <br /> zone while the County should assume the responsibility for controlling <br /> the remainder of the approach zone through some form of airport zoning <br /> to restrict the height of trees, etc. in the flight path. This raises <br /> serious legal 'problems of whether the County can or should put severe <br /> restrictions on the property of adjoining landowners for the benefit <br /> of the airport devellopers. It is one matter for the County to control <br /> airport approach zones through airport zoning when the airport is <br /> owned by the County, but is is quite a different (and highly questionable) <br /> legal matter for the County to apply zoning controls on the approach <br /> zones for a privately owned airport. This would be a case of a gomernmental <br /> body "taking" property of one landowner for the benefit of another. It <br /> is doubtful whether the County could, or would wish to, get involved <br /> in this type of legal quagmire. It is precisely for this reason that <br /> our Zoning Ordinance specifically included item (c) in the list of <br /> requirements for an airport, viz, that "land sufficient to provide <br /> approach zones and overrun areas is owned or controlled h., f-h. <br />
The URL can be used to link to this page
Your browser does not support the video tag.