HF 849

1st Unofficial Engrossment - 81st Legislature (1999 - 2000) Posted on 12/15/2009 12:00am

  1.1                          A bill for an act 
  1.2             relating to airports; defining minor use airport for 
  1.3             certain purposes; limiting the means to expand or 
  1.4             upgrade an existing metropolitan airport from minor 
  1.5             use to intermediate use status without approval in a 
  1.6             law; making legislative findings related to certain 
  1.7             airport matters; defining certain terms; providing for 
  1.8             certain airport impact mitigation planning and airport 
  1.9             tax increment financing districts; authorizing the 
  1.10            issuing of certain obligations by defined cities; 
  1.11            authorizing a metropolitan area airport impact 
  1.12            mitigation bond credit enhancement program by the 
  1.13            metropolitan council; authorizing a contingent 
  1.14            property tax levy in the metropolitan area; amending 
  1.15            Minnesota Statutes 1998, section 473.641, subdivision 
  1.16            4. 
  1.17  BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF MINNESOTA: 
  1.18     Section 1.  Minnesota Statutes 1998, section 473.641, 
  1.19  subdivision 4, is amended to read: 
  1.20     Subd. 4.  [EXPANSION OR UPGRADE OF METRO AIRPORT.] 
  1.21  Notwithstanding any other law, the metropolitan airports 
  1.22  commission shall not use revenue from any source, as described 
  1.23  by section 473.608, for construction of air facilities to expand 
  1.24  or upgrade the use of an existing metropolitan airport from 
  1.25  minor use to intermediate use status as defined by the 
  1.26  metropolitan development guide, aviation chapter, adopted 
  1.27  pursuant to section 473.145 without approval in a law.  For the 
  1.28  purposes of this section, a minor use airport is defined as an 
  1.29  airport with a runway or runways of length no longer than 5,000 
  1.30  feet. 
  1.31     Sec. 2.  [FINDINGS.] 
  2.1      The legislature finds that: 
  2.2      (1) the legislature has directed the metropolitan airports 
  2.3   commission to develop a plan to mitigate aircraft noise 
  2.4   associated with the operation of the Minneapolis/St. Paul 
  2.5   International Airport; 
  2.6      (2) the metropolitan airports commission has developed a 
  2.7   noise mitigation plan in conjunction with communities adjacent 
  2.8   to the airport and is in the process of updating its FAR Part 
  2.9   150 noise mitigation program for submission to and approval by 
  2.10  the Federal Aviation Administration; 
  2.11     (3) the legislature also established the governor's airport 
  2.12  community stabilization funding task force that recommended 
  2.13  further mitigation funding to address federal, state, and local 
  2.14  participation in mitigation of noise and other impacts 
  2.15  associated with expansion of the Minneapolis/St. Paul 
  2.16  International Airport at its present location; 
  2.17     (4) the task force concluded that: 
  2.18     (i) the metropolitan airports commission has committed 
  2.19  significant resources toward mitigating the negative impacts 
  2.20  associated with airport expansion, but the FAR Part 150 noise 
  2.21  program is insufficient to address all impacts; 
  2.22     (ii) the metropolitan airports commission is neither 
  2.23  capable of, nor should it be required to, finance mitigation of 
  2.24  all airport impacts; 
  2.25     (iii) the decision to keep and expand the airport at its 
  2.26  current location was a state decision, and as such, the state 
  2.27  should be a financial partner in mitigation projects resulting 
  2.28  from the expansion of the airport; and 
  2.29     (iv) no single funding source is adequate for the range and 
  2.30  scope of proposed mitigation activities; and 
  2.31     (5) appropriate measures to mitigate adverse impacts 
  2.32  include, but are not limited to, insulation, redevelopment and 
  2.33  housing replacement activities, and property value assurance and 
  2.34  expenditures for all such measures are for a public purpose. 
  2.35     Sec. 3.  [DEFINITIONS.] 
  2.36     Subdivision 1.  [APPLICATION.] For the purposes of sections 
  3.1   2 to 6, the terms defined in this section have the meanings 
  3.2   given them. 
  3.3      Subd. 2.  [AIRPORT IMPACT DISTRICT.] "Airport impact 
  3.4   district" means an airport impact tax increment financing 
  3.5   district described in section 5. 
  3.6      Subd. 3.  [AIRPORT IMPACT ZONE.] "Airport impact zone" 
  3.7   means a contiguous or noncontiguous geographic area designated 
  3.8   by a city and approved by the council as part of a mitigation 
  3.9   plan under section 4. 
  3.10     Subd. 4.  [CITY.] "City" means the cities of Bloomington, 
  3.11  Burnsville, Eagan, Mendota Heights, Minneapolis, Richfield, and 
  3.12  St. Paul or any of them. 
  3.13     Subd. 5.  [COUNCIL.] "Council" means the metropolitan 
  3.14  council.  
  3.15     Subd. 6.  [GOVERNING BODY.] "Governing body" means the city 
  3.16  council of a city. 
  3.17     Subd. 7.  [HOUSING REPLACEMENT ACTIVITIES.] "Housing 
  3.18  replacement activities" means rehabilitation, acquisition, 
  3.19  demolition relocation assistance, relocation of existing 
  3.20  dwelling units, and construction of new dwelling units, for the 
  3.21  purpose of replacing dwelling units eliminated by airport 
  3.22  mitigation activities. 
  3.23     Subd. 8.  [IMPACT REPORT.] "Impact report" means a written 
  3.24  report identifying airport impacts adopted by a city under 
  3.25  section 4. 
  3.26     Subd. 9.  [MITIGATION PLAN.] "Mitigation plan" means a plan 
  3.27  for airport impact mitigation developed by a city and approved 
  3.28  by the council under section 4. 
  3.29     Subd. 10.  [OBLIGATION.] "Obligation" has the meaning given 
  3.30  it in Minnesota Statutes, section 475.51, subdivision 3.  The 
  3.31  term includes obligations issued to refund prior obligations 
  3.32  issued under sections 2 to 6. 
  3.33     Subd. 11.  [SCHOOL DISTRICT.] "School district" means a 
  3.34  school district whose jurisdiction includes all or any portion 
  3.35  of a city. 
  3.36     Sec. 4.  [AIRPORT IMPACT MITIGATION PLANNING.] 
  4.1      Subdivision 1.  [IMPACT REPORT.] A city may study and 
  4.2   identify airport impacts and the scope of those impacts on the 
  4.3   city.  At the conclusion of an impact study, a city must adopt a 
  4.4   report of the impacts on the city.  In studying airport impacts 
  4.5   and preparing a report, a city must take into account airport 
  4.6   noise impacts and additional environmental, transportation, and 
  4.7   economic impacts associated with expansion of the 
  4.8   Minneapolis/St. Paul International Airport.  A city must also 
  4.9   consider and incorporate the overhead noise guidelines 
  4.10  established by the Federal Aviation Administration and 
  4.11  recommendations of the low frequency noise policy committee 
  4.12  concerning noise impacts. 
  4.13     Subd. 2.  [MITIGATION PLAN.] (a) After adopting an airport 
  4.14  impact report, a city must develop an airport mitigation plan 
  4.15  for an airport impact zone in the city.  In developing the 
  4.16  mitigation plan, a city must seek to determine the most 
  4.17  effective measures for mitigating the impacts identified in the 
  4.18  impact report.  A city may consider any measures for mitigating 
  4.19  airport impacts, including, but not limited to, noise insulation 
  4.20  of residential and commercial buildings, land use conversion, 
  4.21  development of housing to replace units lost through mitigation 
  4.22  activities, and property value assurance programs.  The 
  4.23  mitigation plan must include: 
  4.24     (1) designated boundaries of the airport impact zone; 
  4.25     (2) a description of recommended impact mitigation 
  4.26  measures; 
  4.27     (3) if the plan includes establishment of one or more 
  4.28  airport impact tax increment financing districts, the proposed 
  4.29  boundaries of each district consistent with the terms of section 
  4.30  5; 
  4.31     (4) if the plan includes conversion of residential land 
  4.32  use, a description of proposed housing replacement activities; 
  4.33     (5) estimates of costs of the recommended mitigation 
  4.34  measures and possible financing sources; 
  4.35     (6) an analysis of the feasibility of property tax 
  4.36  abatement under Minnesota Statutes, sections 469.1813 to 
  5.1   469.1815, as a financing source; and 
  5.2      (7) the estimated amount of obligations, if any, to be 
  5.3   issued under section 6, including a description of the proposed 
  5.4   security for the obligations and whether the city requests 
  5.5   credit enhancement by the council as provided in section 6, 
  5.6   subdivision 2. 
  5.7      (b) Before initial approval of a mitigation plan, a city 
  5.8   must conduct a public hearing after publishing at least ten days 
  5.9   before the hearing a notice in a newspaper of general 
  5.10  circulation in the city.  The hearing notice must state that the 
  5.11  mitigation plan and the mitigation report are available for 
  5.12  review in the administrative offices of the city.  After initial 
  5.13  approval of the mitigation plan by the governing body, the city 
  5.14  must submit the mitigation plan and the mitigation report to the 
  5.15  council for approval, and must also submit copies to the 
  5.16  metropolitan airports commission for review and comment.  No 
  5.17  more than 60 days after receipt of the city's submission, the 
  5.18  council must approve, disapprove, or otherwise comment on the 
  5.19  mitigation plan.  Failure by the council to approve or comment 
  5.20  within 60 days is considered approval of the mitigation plan.  
  5.21  An action described in a mitigation plan must not be financed by 
  5.22  the mitigation fund or an airport impact district until the 
  5.23  mitigation plan has been approved by the council and then 
  5.24  approved by the governing body. 
  5.25     (c) Before approving any mitigation plan, the council must 
  5.26  establish criteria for evaluating proposed airport impact zones, 
  5.27  airport impact districts, and mitigation measures.  The council 
  5.28  must consult with the cities and the metropolitan airports 
  5.29  commission in developing the criteria.  The council must approve 
  5.30  final criteria by December 31, 2000.  Any mitigation plan 
  5.31  approved under sections 2 to 6 must be consistent with the 
  5.32  criteria established under this paragraph. 
  5.33     (d) A mitigation plan may be changed for the following 
  5.34  purposes after the notice, hearing, and approvals required for 
  5.35  approval of the original plan to: 
  5.36     (1) increase the total estimated cost of mitigation 
  6.1   activities; 
  6.2      (2) increase the total estimated amount of obligations to 
  6.3   be issued; 
  6.4      (3) secure any obligations by the pledge described in 
  6.5   section 6, subdivision 2, if the pledge was not included in the 
  6.6   original plan; 
  6.7      (4) expand the boundaries of an airport impact zone; 
  6.8      (5) create or expand the boundaries of an airport impact 
  6.9   district; or 
  6.10     (6) add mitigation activities beyond the scope of 
  6.11  activities described in the original plan. 
  6.12     (e) Expenditures to implement a mitigation plan are not 
  6.13  considered a business subsidy under Minnesota Statutes, sections 
  6.14  116J.993 to 116J.995. 
  6.15     Sec. 5.  [AIRPORT IMPACT TAX INCREMENT FINANCING 
  6.16  DISTRICTS.] 
  6.17     Subdivision 1.  [AUTHORIZATION.] A city may establish one 
  6.18  or more airport impact tax increment financing districts within 
  6.19  an airport impact zone.  At least 75 percent of the area of an 
  6.20  airport impact district must be located within the 60 DNL 
  6.21  contour surrounding the Minneapolis/St. Paul International 
  6.22  Airport.  The boundaries of each district must be described in a 
  6.23  mitigation plan. 
  6.24     Subd. 2.  [SPECIAL RULES.] (a) An airport impact district 
  6.25  is considered a redevelopment district within the meaning of, 
  6.26  and is subject to, Minnesota Statutes, sections 469.174 to 
  6.27  469.179, except as otherwise provided in this subdivision.  For 
  6.28  the purposes of Minnesota Statutes, section 469.174, subdivision 
  6.29  8, "project" means an airport impact zone described in section 4.
  6.30     (b) For the purposes of Minnesota Statutes, section 
  6.31  469.174, subdivision 10, the governing body must find that 
  6.32  parcels consisting of 70 percent of the area of the district are 
  6.33  occupied by buildings, streets, utilities, or other 
  6.34  improvements, and more than 50 percent of the buildings, not 
  6.35  including outbuildings, currently or upon completion of airport 
  6.36  expansion are reasonably expected to experience airport impacts 
  7.1   identified in the mitigation plan to a degree requiring land use 
  7.2   conversion to accommodate uses compatible with the airport.  
  7.3   This finding may be made at the time of approval of the 
  7.4   mitigation plan. 
  7.5      (c) For the purposes of Minnesota Statutes, section 
  7.6   469.1763, subdivision 2, the in-district percentage is 75 
  7.7   percent, except that any expenditures within the boundaries of 
  7.8   any other airport impact tax increment financing district in the 
  7.9   city are considered activities within the district whenever made 
  7.10  notwithstanding anything to the contrary in Minnesota Statutes, 
  7.11  section 469.1763, subdivision 3, and the 25 percent pooling 
  7.12  percentage may be used only to pay for administrative expenses 
  7.13  and housing replacement activities. 
  7.14     (d) For the purposes of Minnesota Statutes, section 
  7.15  469.176, subdivision 4j, the cost of correcting conditions that 
  7.16  allow designation of the airport impact district includes the 
  7.17  cost of a mitigation measure described in an approved mitigation 
  7.18  plan. 
  7.19     (e) Minnesota Statutes, sections 273.1399 and 469.1782, 
  7.20  subdivision 1, do not apply to the district if the city elects 
  7.21  either or both of the following: 
  7.22     (1) the exemption under Minnesota Statutes, section 
  7.23  273.1399, subdivision 6, paragraph (d); or 
  7.24     (2) at least 15 percent of the revenue generated from tax 
  7.25  increments from the airport impact district in any year is 
  7.26  deposited in the housing replacement account of the city and 
  7.27  spent for housing replacement activities described in the 
  7.28  mitigation plan. 
  7.29     (f) Housing replacement activities may be located in the 
  7.30  city within or outside the airport impact district. 
  7.31     (g) Minnesota Statutes, chapter 473F, does not apply to 
  7.32  property within an airport impact district beginning in the 
  7.33  first year in which tax increment is paid to the city and 
  7.34  continuing until decertification of the district.  Tax increment 
  7.35  from the district is calculated according to Minnesota Statutes, 
  7.36  section 469.177, subdivision 3, paragraph (a), without regard to 
  8.1   the fiscal disparities provisions of Minnesota Statutes, chapter 
  8.2   473F. 
  8.3      Sec. 6.  [BONDS; SECURITY.] 
  8.4      Subdivision 1.  [TERMS.] (a) A city may issue obligations 
  8.5   secured by: 
  8.6      (1) tax increments; 
  8.7      (2) abatements; 
  8.8      (3) any other revenues available to the city under law; or 
  8.9      (4) any combination of revenue described in clauses (1) to 
  8.10  (3). 
  8.11     (b) The proceeds of obligations must be used to pay or 
  8.12  reimburse any costs to implement a mitigation plan, including, 
  8.13  without limitation, costs of preparing the impact report and the 
  8.14  mitigation plan.  The governing body may provide by resolution 
  8.15  that the obligations are additionally secured by the full faith 
  8.16  and credit of the city.  Notwithstanding any other law or 
  8.17  charter provision, voter approval is not required and net debt 
  8.18  limits do not apply to obligations issued under this section.  
  8.19  Obligations secured in whole or in part with tax increments from 
  8.20  an airport impact district must be issued according to sections 
  8.21  2 to 6 and Minnesota Statutes, section 469.178. 
  8.22     Subd. 2.  [METROPOLITAN AREA CREDIT ENHANCEMENT 
  8.23  PROGRAM.] (a) The council may establish an airport impact 
  8.24  mitigation bond credit enhancement program as provided in this 
  8.25  section.  The council may pledge its full faith and credit and 
  8.26  taxing powers to obligations issued under sections 2 to 6 if: 
  8.27     (1) the city so requests and the council approves that 
  8.28  pledge as part of the city's mitigation plan; and 
  8.29     (2) the council finds that revenues pledged for payment of 
  8.30  the obligations will produce, as estimated at the time of the 
  8.31  pledge, at least 125 percent of the principal and interest due 
  8.32  on the obligations. 
  8.33     (b) The pledge must be made by resolution of the council.  
  8.34  Voter approval of obligations secured by the pledge described in 
  8.35  this subdivision is not required and net debt limits do not 
  8.36  apply. 
  9.1      (c) Before pledging its full faith and credit, the council 
  9.2   must, in consultation with the cities and the metropolitan 
  9.3   airports commission, establish criteria for approving requests 
  9.4   for credit enhancement under this section.  The criteria may 
  9.5   contain limits on the total amount of obligations that may be 
  9.6   credit enhanced under this subdivision. 
  9.7      (d) If there is a deficiency in revenues pledged to 
  9.8   obligations credit enhanced under this subdivision, the council 
  9.9   must levy a tax against all taxable property in the metropolitan 
  9.10  area and advance the proceeds of the levy to the city for 
  9.11  deposit in the debt service fund for the obligations.  The city 
  9.12  must reimburse the council for the advance to the extent the 
  9.13  deficient revenues are later collected. 
  9.14     (e) Taxes levied by the council because of credit 
  9.15  enhancement under this subdivision do not affect the amount or 
  9.16  rate of taxes that may be levied by the council for other 
  9.17  purposes and are not subject to limit as to rate or amount. 
  9.18     (f) The council and each city that participates in the 
  9.19  credit enhancement program may enter into agreements they 
  9.20  determine to be necessary to implement the credit enhancement 
  9.21  program.  The agreements may extend over any period, 
  9.22  notwithstanding any law to the contrary. 
  9.23     Sec. 7.  [APPLICATION.] 
  9.24     Section 1 applies in the counties of Anoka, Carver, Dakota, 
  9.25  Hennepin, Ramsey, Scott, and Washington.  Sections 2, 3, 4, and 
  9.26  6 do not require local approval because Minnesota Statutes, 
  9.27  section 645.023, subdivision 1, paragraph (a), applies.  
  9.28  Sections 2, 3, 4, and 6 are effective June 1, 2000.  Section 5 
  9.29  is effective for each of the cities of Bloomington, Burnsville, 
  9.30  Eagan, Mendota Heights, Minneapolis, Richfield, and St. Paul the 
  9.31  day after the governing body of each city and its chief clerical 
  9.32  officer, together with the governing body of each affected 
  9.33  county and school district and its chief clerical officer, 
  9.34  timely complete their compliance with Minnesota Statutes, 
  9.35  sections 469.1782, subdivision 2, and 645.021, subdivisions 2 
  9.36  and 3.