Skip to main content Skip to office menu Skip to footer
Capital IconMinnesota Legislature

HF 3258

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

KEY: stricken = removed, old language.
underscored = added, new language.
  1.1                          A bill for an act 
  1.2             relating to Minneapolis-St. Paul International 
  1.3             Airport; providing for the impact of expansion of the 
  1.4             Minneapolis-St. Paul International Airport; 
  1.5             authorizing airport mitigation planning, the 
  1.6             establishment of airport impact zones, and tax 
  1.7             increment financing districts in the cities of 
  1.8             Bloomington, Burnsville, Eagan, Mendota Heights, 
  1.9             Minneapolis, Richfield, and St. Paul; creating an 
  1.10            airport impact mitigation fund in the state treasury; 
  1.11            authorizing certain related activities by the 
  1.12            department of trade and economic development; 
  1.13            authorizing a metropolitan area credit enhancement 
  1.14            program including a contingent metropolitan area 
  1.15            property tax levy; appropriating money. 
  1.16  BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF MINNESOTA: 
  1.17     Section 1.  [DEFINITIONS.] 
  1.18     Subdivision 1.  [APPLICATION.] For the purposes of this 
  1.19  act, the terms defined in this section have the meanings given 
  1.20  them. 
  1.21     Subd. 2.  [AIRPORT IMPACT DISTRICT.] "Airport impact 
  1.22  district" means an airport impact tax increment financing 
  1.23  district described in section 3. 
  1.24     Subd. 3.  [AIRPORT IMPACT ZONE.] "Airport impact zone" 
  1.25  means a contiguous or noncontiguous geographic area designated 
  1.26  by a city and approved by the commissioner as part of a 
  1.27  mitigation plan under section 2. 
  1.28     Subd. 4.  [AIRPORT SALES.] "Airport sales" means sales that 
  1.29  are taxable under Minnesota Statutes, chapter 297A, and occur on 
  1.30  property owned by the metropolitan airports commission at the 
  2.1   Minneapolis-St. Paul International Airport including, without 
  2.2   limit, parking, vehicle rental, food and beverage, vending, 
  2.3   merchandise, and pay telephones.  Airport sales do not include 
  2.4   sales of goods or taxable services purchased by the metropolitan 
  2.5   airports commission or by persons or entities conducting a 
  2.6   private trade or business on property owned by the metropolitan 
  2.7   airports commission at the Minneapolis-St. Paul International 
  2.8   Airport. 
  2.9      Subd. 5.  [CITY.] "City" means the cities of Bloomington, 
  2.10  Burnsville, Eagan, Mendota Heights, Minneapolis, Richfield, and 
  2.11  St. Paul, or any of them. 
  2.12     Subd. 6.  [COMMISSIONER.] "Commissioner" means the 
  2.13  commissioner of trade and economic development. 
  2.14     Subd. 7.  [COUNCIL.] "Council" means the metropolitan 
  2.15  council. 
  2.16     Subd. 8.  [DEPARTMENT.] "Department" means the department 
  2.17  of trade and economic development. 
  2.18     Subd. 9.  [GOVERNING BODY.] "Governing body" means the city 
  2.19  council of a city. 
  2.20     Subd. 10.  [HOUSING REPLACEMENT ACTIVITIES.] "Housing 
  2.21  replacement activities" means rehabilitation, acquisition, 
  2.22  relocation assistance, relocation of existing dwelling units, 
  2.23  and construction of new dwelling units, for the purpose of 
  2.24  replacing dwelling units eliminated by airport mitigation 
  2.25  activities. 
  2.26     Subd. 11.  [IMPACT REPORT.] "Impact report" means a written 
  2.27  report identifying airport impacts adopted by a city under 
  2.28  section 2. 
  2.29     Subd. 12.  [MITIGATION FUND.] "Mitigation fund" means the 
  2.30  airport impact mitigation fund established under section 4. 
  2.31     Subd. 13.  [MITIGATION PLAN.] "Mitigation plan" means a 
  2.32  plan for airport impact mitigation developed by a city and 
  2.33  approved by the commissioner under section 2. 
  2.34     Subd. 14.  [OBLIGATION.] "Obligation" has the meaning given 
  2.35  it in Minnesota Statutes, section 475.51, subdivision 3.  The 
  2.36  term includes obligations issued to refund prior obligations 
  3.1   issued under this act. 
  3.2      Subd. 15.  [SCHOOL DISTRICT.] "School district" means a 
  3.3   school district whose jurisdiction includes all or any portion 
  3.4   of a city. 
  3.5      Sec. 2.  [AIRPORT IMPACT MITIGATION PLANNING.] 
  3.6      Subdivision 1.  [IMPACT REPORT.] A city may study and 
  3.7   identify airport impacts and the scope of those impacts on the 
  3.8   city.  At the conclusion of an impact study, a city must adopt a 
  3.9   report of the impacts on the city.  In studying airport impacts 
  3.10  and preparing a report, a city must take into account airport 
  3.11  noise impacts and additional environmental, transportation, and 
  3.12  economic impacts associated with expansion of the 
  3.13  Minneapolis-St. Paul International Airport.  A city must also 
  3.14  consider and incorporate the overhead noise guidelines 
  3.15  established by the federal aviation administration and 
  3.16  recommendations of the Low Frequency Noise Policy Committee 
  3.17  concerning noise impacts. 
  3.18     Subd. 2.  [MITIGATION PLAN.] (a) After adopting an airport 
  3.19  impact report, a city must develop an airport mitigation plan 
  3.20  for an airport impact zone in the city.  In developing the 
  3.21  mitigation plan, a city must seek to determine the most 
  3.22  effective measures for mitigating the impacts identified in the 
  3.23  impact report.  A city may consider any measures for mitigating 
  3.24  airport impacts including, but not limited to, noise insulation 
  3.25  of residential and commercial buildings, land use conversion, 
  3.26  development of housing to replace units lost through mitigation 
  3.27  activities, and property value assurance programs.  The 
  3.28  mitigation plan must include: 
  3.29     (1) designated boundaries of the airport impact zone; 
  3.30     (2) a description of recommended impact mitigation 
  3.31  measures; 
  3.32     (3) if the plan includes establishment of one or more 
  3.33  airport impact tax increment financing districts, the proposed 
  3.34  boundaries of each district, consistent with the terms of 
  3.35  section 3; 
  3.36     (4) if the plan includes conversion of residential land 
  4.1   use, a description of proposed housing replacement activities; 
  4.2      (5) estimates of costs of the recommended mitigation 
  4.3   measures and possible financing sources; 
  4.4      (6) an analysis of the feasibility of property tax 
  4.5   abatement under Minnesota Statutes, sections 469.1813 to 
  4.6   469.1815 as a financing source; and 
  4.7      (7) the estimated amount of obligations, if any, to be 
  4.8   issued under this act, including a description of the proposed 
  4.9   security for the obligations and whether the city requests 
  4.10  credit enhancement by the council as provided in section 5, 
  4.11  subdivision 2. 
  4.12     (b) Before initial approval of a mitigation plan, a city 
  4.13  must conduct a public hearing after publishing at least ten days 
  4.14  before the hearing a notice in a newspaper of general 
  4.15  circulation in the city.  The hearing notice must state that the 
  4.16  mitigation plan and the mitigation report are available for 
  4.17  review in the administrative offices of the city.  After initial 
  4.18  approval of the mitigation plan by the governing body, the city 
  4.19  must submit the mitigation plan and the mitigation report to the 
  4.20  commissioner for approval, and must also submit copies to the 
  4.21  council and the metropolitan airports commission for review and 
  4.22  comment.  Not more than 60 days after receipt of the city's 
  4.23  submission, the commissioner must approve, disapprove, or 
  4.24  otherwise comment on the mitigation plan.  Failure by the 
  4.25  commissioner to approve or comment within 60 days is considered 
  4.26  approval of the mitigation plan.  An action described in a 
  4.27  mitigation plan must not be financed by the mitigation fund or 
  4.28  an airport impact district until the mitigation plan has been 
  4.29  approved by the commissioner and then approved by the governing 
  4.30  body. 
  4.31     (c) Before approving any mitigation plan, the commissioner 
  4.32  must establish criteria for evaluating proposed airport impact 
  4.33  zones, airport impact districts, and mitigation measures.  The 
  4.34  commissioner must consult with the cities, the council, and the 
  4.35  metropolitan airports commission in developing the criteria.  
  4.36  The commissioner must approve final criteria by December 31, 
  5.1   2000.  Any mitigation plan approved under this act must be 
  5.2   consistent with the criteria established under this paragraph. 
  5.3      (d) If the mitigation plan, or any amendment under 
  5.4   paragraph (e), clause (3), includes credit enhancement by the 
  5.5   council as provided in section 5, subdivision 2, the mitigation 
  5.6   plan must also be approved by the council before issuance of 
  5.7   bonds secured under section 5, subdivision 2. 
  5.8      (e) A mitigation plan may be changed after the notice, 
  5.9   hearing, and approvals required for approval of the original 
  5.10  plan.  The change is required only to: 
  5.11     (1) increase the total estimated cost of mitigation 
  5.12  activities; 
  5.13     (2) increase the total estimated amount of obligations to 
  5.14  be issued; 
  5.15     (3) secure any obligations by the pledge described in 
  5.16  section 5, subdivision 2, if the pledge was not included in the 
  5.17  original plan; 
  5.18     (4) expand the boundaries of an airport impact zone; 
  5.19     (5) create or expand the boundaries of an airport impact 
  5.20  district; or 
  5.21     (6) add mitigation activities beyond the scope of 
  5.22  activities described in the original plan. 
  5.23     (f) Expenditures to implement a mitigation plan are not 
  5.24  considered a business subsidy under Minnesota Statutes, sections 
  5.25  116J.993 to 116J.995. 
  5.26     Sec. 3.  [AIRPORT IMPACT TAX INCREMENT FINANCING 
  5.27  DISTRICTS.] 
  5.28     Subdivision 1.  [AUTHORIZATION.] A city may establish one 
  5.29  or more airport impact tax increment financing districts within 
  5.30  an airport impact zone.  At least 75 percent of the area of an 
  5.31  airport impact district must be located within the 60 DNL 
  5.32  contour surrounding the Minneapolis-St. Paul International 
  5.33  Airport.  The boundaries of each district must be described in a 
  5.34  mitigation plan. 
  5.35     Subd. 2.  [SPECIAL RULES.] (a) An airport impact district 
  5.36  is considered a redevelopment district within the meaning of, 
  6.1   and is subject to, Minnesota Statutes, sections 469.174 to 
  6.2   469.179, except as otherwise provided in this subdivision.  For 
  6.3   the purposes of Minnesota Statutes, section 469.174, subdivision 
  6.4   8, "project" means an airport impact zone described in section 2.
  6.5      (b) For the purposes of Minnesota Statutes, section 
  6.6   469.174, subdivision 10, the governing body must find that 
  6.7   parcels consisting of 70 percent of the area of the district are 
  6.8   occupied by buildings, streets, utilities, or other 
  6.9   improvements, and more than 50 percent of the buildings, not 
  6.10  including outbuildings, currently or upon completion of airport 
  6.11  expansion are reasonably expected to experience airport impacts 
  6.12  identified in the mitigation plan to a degree requiring land use 
  6.13  conversion to accommodate uses compatible with the airport.  
  6.14  This finding may be made at the time of approval of the 
  6.15  mitigation plan. 
  6.16     (c) For the purposes of Minnesota Statutes, section 
  6.17  469.1763, subdivision 2, the "in-district percentage" is 75 
  6.18  percent, except that any expenditures within the boundaries of 
  6.19  any other airport impact tax increment financing district in the 
  6.20  city are considered activities within the district whenever made 
  6.21  notwithstanding anything to the contrary in Minnesota Statutes, 
  6.22  section 469.1763, subdivision 3, and the 25 percent "pooling 
  6.23  percentage" may be used only to pay for administrative expenses 
  6.24  and housing replacement activities. 
  6.25     (d) For the purposes of Minnesota Statutes, section 
  6.26  469.176, subdivision 4j, the cost of correcting conditions that 
  6.27  allow designation of the airport impact district includes the 
  6.28  cost of a mitigation measure described in an approved mitigation 
  6.29  plan. 
  6.30     (e) Minnesota Statutes, sections 273.1399 and 469.1782, 
  6.31  subdivision 1, do not apply to the district if the city elects 
  6.32  either or both of the following: 
  6.33     (1) the exemption under Minnesota Statutes, section 
  6.34  273.1399, subdivision 6, paragraph (d); or 
  6.35     (2) at least 15 percent of the revenue generated from tax 
  6.36  increments from the airport impact district in any year is 
  7.1   deposited in the housing replacement account of the city and 
  7.2   spent for housing replacement activities described in the 
  7.3   mitigation plan. 
  7.4      (f) Housing replacement activities may be located in the 
  7.5   city within or outside the airport impact district. 
  7.6      (g) Minnesota Statutes, chapter 473F, does not apply to 
  7.7   property within an airport impact district beginning in the 
  7.8   first year in which tax increment is paid to the city and 
  7.9   continuing until decertification of the district.  Tax increment 
  7.10  from the district is calculated according to Minnesota Statutes, 
  7.11  section 469.177, subdivision 3, clause (a), without regard to 
  7.12  the fiscal disparities provisions of Minnesota Statutes, chapter 
  7.13  473F. 
  7.14     Sec. 4.  [AIRPORT IMPACT MITIGATION FUND.] 
  7.15     Subdivision 1.  [FUND CREATED; SOURCES.] The airport impact 
  7.16  mitigation fund is established in the state treasury.  The 
  7.17  mitigation fund is administered by the commissioner for the 
  7.18  purposes described in this section. 
  7.19     Subd. 2.  [INCREMENTAL AIRPORT SALES TAX.] Notwithstanding 
  7.20  anything to the contrary in Minnesota Statutes, section 297A.44, 
  7.21  to the extent revenues derived from sales taxes imposed under 
  7.22  Minnesota Statutes, chapter 297A, on airport sales exceed 
  7.23  $12,000,000 in any fiscal year, the excess revenues are 
  7.24  appropriated annually to the mitigation fund beginning in the 
  7.25  fiscal year ending in 2001 and ending in the fiscal year ending 
  7.26  in 2025. 
  7.27     Subd. 3.  [GENERAL FUND APPROPRIATION.] (a) $2,000,000 is 
  7.28  appropriated from the general fund to the mitigation fund.  The 
  7.29  appropriation is available until spent. 
  7.30     (b) To ensure adequate funding to meet long-term airport 
  7.31  mitigation needs under this act, the legislature declares as 
  7.32  policy its intent to appropriate $4,000,000 in each of the 
  7.33  following four biennia 2001-2002 through 2007-2008 and 
  7.34  $2,000,000 in the first year of the 2009-2010 biennium, for a 
  7.35  total of $20,000,000 appropriated over that ten-year period, 
  7.36  including the appropriation in paragraph (a). 
  8.1      Subd. 4.  [USE OF REVENUES.] Amounts in the mitigation fund 
  8.2   may be spent only for the following purposes: 
  8.3      (1) to pay principal of, interest on, and redemption 
  8.4   premium, if any, on obligations issued by a city under this act; 
  8.5      (2) to pay or reimburse a city for costs incurred to 
  8.6   implement a mitigation plan, including, without limit, costs of 
  8.7   preparing the impact report and mitigation plan; 
  8.8      (3) to pay a school district to mitigate decreases in 
  8.9   student population created by mitigation activities of a city 
  8.10  under the city's mitigation plan; and 
  8.11     (4) by the department to pay the costs of administering the 
  8.12  mitigation fund and related activities of the department under 
  8.13  this act. 
  8.14     Subd. 5.  [PAYMENT PROVISIONS.] (a) Before disbursing any 
  8.15  amounts from the mitigation fund, the commissioner must 
  8.16  establish criteria for selecting activities identified in 
  8.17  subdivision 4 to be financed from the fund.  The commissioner 
  8.18  must consult with the cities, the school districts, the council 
  8.19  and the metropolitan airports commission in developing the 
  8.20  criteria.  The commissioner must approve final criteria by 
  8.21  December 31, 2000.  The criteria must identify priorities for 
  8.22  funding, taking into account: 
  8.23     (1) the severity of airport impacts among the cities and 
  8.24  school districts; 
  8.25     (2) the type of mitigation measures required in order to 
  8.26  address the impacts; 
  8.27     (3) the cost of impact mitigation activities identified in 
  8.28  the mitigation plans; 
  8.29     (4) the amount of obligations to be issued under this act 
  8.30  as identified in the mitigation plans; and 
  8.31     (5) the amount of other revenues available to pay the costs 
  8.32  identified in subdivision 4. 
  8.33     (b) The commissioner may establish procedures for 
  8.34  administration of the mitigation fund as necessary, including 
  8.35  without limitation a process for applications, disbursement, and 
  8.36  reporting of expenditures. 
  9.1      Subd. 6.  [TERMINATION OF MITIGATION FUND.] The mitigation 
  9.2   fund ends on the earlier of: 
  9.3      (1) the date by which all cities and school districts have 
  9.4   notified the commissioner that all costs payable from the 
  9.5   mitigation fund under this act have been paid; or 
  9.6      (2) the end of the fiscal year ending in 2030.  
  9.7   The balance of amounts in the mitigation fund on its termination 
  9.8   are credited to the state general fund. 
  9.9      Sec. 5.  [BONDS; SECURITY.] 
  9.10     Subdivision 1.  [TERMS.] (a) A city may issue obligations 
  9.11  secured by 
  9.12     (1) tax increments, 
  9.13     (2) abatements, 
  9.14     (3) amounts disbursed from the airport mitigation fund, 
  9.15     (4) any other revenues available to the city under law, or 
  9.16     (5) any combination of revenue described in clauses (1) to 
  9.17  (4).  
  9.18     (b) The proceeds of obligations must be used to pay or 
  9.19  reimburse any costs to implement a mitigation plan, including, 
  9.20  without limit, costs of preparing the impact report and the 
  9.21  mitigation plan.  The governing body may provide by resolution 
  9.22  that the obligations are additionally secured by the full faith 
  9.23  and credit of the city.  Notwithstanding any other law or 
  9.24  charter provision, voter approval is not required and net debt 
  9.25  limits do not apply to obligations issued under this section.  
  9.26  Obligations secured in whole or in part with tax increments from 
  9.27  an airport impact district must be issued according to Minnesota 
  9.28  Statutes, section 469.178, and this act. 
  9.29     Subd. 2.  [METROPOLITAN AREA CREDIT ENHANCEMENT 
  9.30  PROGRAM.] (a) The council may establish an airport impact 
  9.31  mitigation bond credit enhancement program as provided in this 
  9.32  section.  The council may pledge its full faith and credit and 
  9.33  taxing powers to obligations issued under this act if: 
  9.34     (1) the city so requests and the commissioner and the 
  9.35  council approves that pledge as part of the city's mitigation 
  9.36  plan; and 
 10.1      (2) the council finds that revenues pledged for payment of 
 10.2   the obligations will produce, as estimated at the time of the 
 10.3   pledge, at least 125 percent of the principal and interest due 
 10.4   on the obligations. 
 10.5      (b) The pledge must be made by resolution of the council.  
 10.6   Voter approval of obligations secured by the pledge described in 
 10.7   this subdivision is not required and net debt limits do not 
 10.8   apply. 
 10.9      (c) Before pledging its full faith and credit, the council 
 10.10  must establish criteria for approving requests for credit 
 10.11  enhancement under this section.  The council must establish 
 10.12  criteria in consultation with the cities, the commissioner, and 
 10.13  the metropolitan airports commission.  The criteria must set 
 10.14  forth priorities for credit enhancement that are consistent with 
 10.15  the priorities established by the commissioner for disbursement 
 10.16  from the mitigation fund under section 4, and may contain limits 
 10.17  on the total amount of obligations that may be credit enhanced 
 10.18  under this subdivision. 
 10.19     (d) If there is a deficiency in revenues pledged to 
 10.20  obligations credit enhanced under this subdivision, the council 
 10.21  must levy a tax against all taxable property in the metropolitan 
 10.22  area and advance the proceeds of the levy to the city for 
 10.23  deposit in the debt service fund for the obligations.  The city 
 10.24  must reimburse the council for the advance to the extent the 
 10.25  deficient revenues are later collected. 
 10.26     (e) Taxes levied by the council because of credit 
 10.27  enhancement under this subdivision do not affect the amount or 
 10.28  rate of taxes that may be levied by the council for other 
 10.29  purposes and are not subject to limit as to rate or amount. 
 10.30     (f) The council and each city that participates in the 
 10.31  credit enhancement program may enter into agreements they 
 10.32  determine to be necessary to implement the credit enhancement 
 10.33  program.  The agreements may extend over any period, 
 10.34  notwithstanding any law to the contrary. 
 10.35     Sec. 6.  [LOCAL APPROVAL; APPLICATION; EFFECTIVE DATES.] 
 10.36     Sections 1, 2, 4, and 5 do not require local approval, 
 11.1   because Minnesota Statutes, section 645.023, subdivision 1, 
 11.2   clause (a), applies.  Section 5 applies in the counties of 
 11.3   Anoka, Carver, Dakota, Hennepin, Ramsey, Scott, and Washington.  
 11.4   Sections 1, 2, 4, and 5, are effective June 1, 2000.  Section 3 
 11.5   is effective for each of the cities of Bloomington, Burnsville, 
 11.6   Eagan, Mendota Heights, Minneapolis, Richfield, and St. Paul the 
 11.7   day after the governing body of each city and its chief clerical 
 11.8   officer timely complete their compliance with Minnesota 
 11.9   Statutes, section 645.021, subdivisions 2 and 3, and section 
 11.10  469.1782, subdivision 2.