Driggs Airport Meeting with the FAA
March 4, 2010


The FAA finally decided to ask for public input to the hangar home prohibition effective September 30, 2009, by visiting Erie CO, Independence OR, Sandpoint ID, and Driggs ID.  Although the FAA mentioned only 70 people had commented on the draft implementation letter by Charles Erhard by the December 21, 2009, deadline, they neglected to mention that only the alphabet groups were asked to comment.  No public comment was solicited.

This public input meeting was probably stimulated by the pending amendment to the FAA appropriations bill introduced by Congressman Sam Graves (R, MO) that classifies TTF agreements including hangar residences as compatible airport adjacent land use.  Although the FAA personnel denied this was the stimulus of their visit, since they made no other effort to get public input during the 5190.6b directive six month comment period which ends March 31, 2010.   I doubt their last minute push for input could come from anywhere else.

The FAA personnel had a PowerPoint they used to remind them of examples of problems with TTF agreements  including six really off point examples.  They also had multiple unsupported and/or false claims in the document.

I do believe the FAA personnel realize the stiff opposition they have fomented with 5190.6b and its prohibition of hangar homes and opposition to all TTF agreements.  The FAA personnel also seemed to understand that each airport is different and it may be difficult to establish one size fits all but they did seem to imply the prohibition will not be a viable policy and they will have to do something more reasonable.

They have asked the group of interested parties at Driggs (airport board, TTF agreement holders, Town Council, City and County zoning officials) to formulate a plan that we thing will work for the TTF hangar residence.  This group has already started meeting to put together a coherent plan for the FAA.

200 OK


The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.