FW: Kalispell City Airport Response (3)Option 1 - Do Nothing: Leave Runway 13-31 in its current location and
orientation and perform minimal upgrades to improve safety at the
Airport.
This option would not meet FAA design standards for the projected
critical aircraft and would therefore not be eligible for any Federal
funding assistance. Without FAA involvement, there are essentially no
issues with development; the City could pursue what ever improvements
they deem appropriate. Stelling would recommend that the City try to
achieve compliance with the minimum ARC design standards which would be
Design Group I (DG-I) - Small Aircraft Exclusively (SAE). Small
aircraft are planes weighing less than 12,500 pounds; Design Group I
aircraft are planes with wingspans less than 49'. The following is a
brief summary of the issues and the feasibility of meeting DG-I (SAE)
standards:
o Runway 13-31 - Existing runway width of 60' meets minimum width for
DG-I; the existing length will accommodate 75% of the GA fleet.
o Runway Object Free Area - A total width of 250' (125' each side of
centerline) is required. Additional land and clearing would be required
on both sides at the south third of runway.
o Runway Protection Zones - This requirement is not directly related
to the Design Group but is a function of the Approach Category (A, B,
etc.) and Approach Visibility Minimums. The minimum requirement for
Small Aircraft Exclusively and visual approaches is a trapezoidal area
250' x 450' x 1,000' beginning 200' from each runway end. The current
location of Runway 13-31 does not place the RPZ's on airport property as
the FAA would require. Since Option 2 directly addresses a shift to the
south and an extension, this option will not comply with FAA standards
for RPZ's.
o Taxiways - The two existing parallel taxiways are too close to
Runway 13-31. DG-I standards require a minimum separation of 150'
between parallel taxiways and runways. Kalispell City Airport's taxiway
separation is 90'. In addition to the separation, the existing taxiways
do not meet the minimum width requirements for DG-I standards. The
existing taxiways are 20' wide; DG-I standards require 25' wide
taxiways. Different options are possible to construct new parallel
taxiways that meet DG-I standards. Each option will have different
issues associated with it. For example, if additional land is not
acquired on the west side of the runway and south of the connector
taxiway, there will not be sufficient land to extend the parallel
taxiway to Runway 31. To establish the feasibility of meeting DG-I
taxiway standards for all of the options will require further
evaluation.
o Part 77 Airspace - The current ALP does not include information on
Part 77 airspace pertaining to the existing runway and is therefore
difficult to evaluate without significant effort. Some basic
observations are that the KGEZ radio towers are penetrations to the
Runway 31 approach surface and are considered by the FAA to be hazardous
to air navigation. There also appears to be transitional surface (7:1)
penetrations by the Hilton, Rosauers, and Murdochs.
Option 1 Summary - Some property acquisition would be required to
establish the Runway OFA on airport property and total reconstruction of
the taxiways will be necessary to comply with the absolute minimum
design standards established by the FAA. The west side parallel taxiway
could not be extended to the end of Runway 31 without additional land
acquisition. Finally, this option would not meet the FAA's minimum RPZ
requirements. The FAA would not participate in or support Option 1
since it does not meet B-II design standards or RPZ requirements.
Option 2 - Do Nothing: Leave Runway 13-31 in its current location and
orientation but shift it to the south to meet the minimum RPZ
requirements for Runway 13 and extend to a length of 4,200'.
This option would not meet FAA design standards for the projected
critical aircraft and would therefore not be eligible for any Federal
funding assistance. The FAA has stated that they will not support
development of an ARC B-I facility at the Kalispell City Airport. This
option is intended to meet Design Group I (DG-I) standards and is
therefore similar to Option 1. The southerly shift and extension to
4,200' are the elements that differentiate it from Option 1. There are
two sub-categories of the DG-I group: Small Aircraft Exclusively (SAE)
and Not Exclusively Small Aircraft (NESA). SAE planes are those
weighing less than 12,500 pounds while NESA planes are those weighing
more than 12,500; Design Group I aircraft are planes with wingspans less
than 49'. The following is a brief summary of the issues and the
feasibility of meeting DG-I standards with respect to both SAE and NESA
standards:
o Runway 13-31 - Existing runway width of 60' meets minimum width for
DG-I both SAE and NESA. Constructing to a length of 4,200' with a
southerly shift of 700' will require the acquisition of several
commercial properties fronting US Highway 93 and the removal of several
buildings from these properties.
o Runway Object Free Area - A total width of 250' (125' each side of
centerline) is required for SAE; a total width of 400' (200' each side
of centerline) is required for NESA. Additional land and clearing would
be required on both sides of the runway at the south third of runway to
comply with SAE and NESA requirements.
o Runway Protection Zones - This requirement is not directly related
to the Design Group but is a function of the Approach Category (A, B,
etc.) and Approach Visibility Minimums. The minimum requirement for
Small Aircraft Exclusively and visual approaches is a trapezoidal area
250' x 450' x 1,000' beginning 200' from each runway end. The current
location of Runway 13-31 does not place the RPZs on airport property as
the FAA would require. To meet this requirement would require shifting
the runway approximately 700' to the south. Additional land would be
required to the south for a 700' shift and a 600' extension. The
additional land needed would include portions of commercial property
abutting US Highway 93 and a small corner of the property owned by the
Wise family.
o Taxiways - The two existing parallel taxiways are too close to
Runway 13-31. SAE standards require a minimum separation of 150'
between parallel taxiways and runways; NESA standards require a minimum
of 225' of separation. Kalispell City Airport's taxiway separation is
only 90'. In addition to the separation, the existing taxiways do not
meet the minimum width requirements for DG-I standards. The existing
taxiways are 20' wide; DG-I standards (Both SAE and NESA) require 25'
wide taxiways. It will not be possible to have a parallel taxiway on
the east side of the runway that meets DG-I NESA requirements. Rosauers
is too close to the existing runway to provide the separation and object
free areas that are required. It would be possible to meet DG-I SAE
standards, however. Different options are possible to construct new
parallel taxiways that meet DG-I SAE standards. Each option will have
different issues associated with it. To establish the feasibility of
meeting DG-I SAE taxiway standards will require further evaluation.
o Part 77 Airspace - The current ALP does not include information on
Part 77 airspace pertaining to the existing runway and is therefore
difficult to evaluate without significant effort. Some basic
observations are that the KGEZ radio towers are penetrations to the
Runway 31 approach surface and are considered by the FAA to be hazardous
to air navigation. There also appears to be transitional surface (7:1)
penetrations by the Hilton, Rosauers, and Murdochs.
Option 2 Summary - Significant property acquisition would be required to
shift and extend the runway to the south and establish the Runway OFA on
airport property. Several businesses fronting US Highway 93 would need
to be relocated to accommodate the shift and extension. Total
reconstruction of the taxiways will be necessary to comply with the
absolute minimum design standards established by the FAA. The west side
parallel taxiway could be extended to the end of Runway 31 with a minor
amount of additional land acquisition. The FAA would not participate in
or support Option 2 since it does not meet B-II design standards.
Option 3 - Reconstruct the runway to B-II standards along a 14-32
orientation to a length of 3,700'.
The FAA would support the planning and construction of the new runway to
DG-II standards but would not support a runway length limited to 3,700'.
The FAA has indicated that they will support a planning of length of
4,280' which would accommodate 95% of the GA fleet; planning to the
ultimate length for 100% of the GA fleet would not be required for FAA
support. Since a minimum runway length of 4,280' would be required for
FAA support, the issues pertaining to this options will be presented in
that context. This is essentially the option shown on the current ALP
but 500' shorter. The following is a brief summary of the issues and
the feasibility of meeting DG-II standards on a rotated or skewed
alignment and a length of 4,280':
o Runway 14-32 - New runway is constructed to a width of 75' to meet
DG-II standards. As noted above, the FAA would require planning to a
length that accommodates 95% of the GA fleet or 4,280'. Substantial
land acquisition would be required for the rotated alignment, southerly
shift, and extension to 4,280'. All of the new property acquisition
shown on the current Exhibit A Property Map would be required. However,
Cemetery Road would not need to be relocated.
o Runway Object Free Area - A total width of 500' (250' each side of
centerline) is required for DG-II standards. All of the new property
acquisition shown on the current Exhibit A Property Map would be
required to protect the OFA.
o Runway Protection Zones - This requirement is not directly related
to the Design Group but is a function of the Approach Category (A, B,
etc.) and Approach Visibility Minimums. The requirement for Aircraft
Approach Categories A and B with visual approaches (or NPI not lower
than 1 mile) is a trapezoidal area 500' x 700' x 1,000' beginning 200'
from each runway end. The proposed location of Runway 14-32 (as shown on
the ALP) would place the Runway 14 RPZ on airport property; the Runway
32 RPZ would require land acquisition to comply with FAA requirements.
o Taxiways - This option plans for the reconstruction of the taxiways
to DG-II standards. The proposed land acquisition includes the property
necessary to construct the new taxiways that comply with FAA design
standards.
o Part 77 Airspace - This option minimizes obstructions to the Part 77
airspace created by structures fronting US Highway 93. The FAA will
still require that the KGEZ radio towers be removed before they will
support improvements at Kalispell City Airport.
Option 3 Summary - This option will only garner FAA support if the
planned length of Runway 14-32 is 4,280' to accommodate 95% of the GA
fleet. The City would not necessarily need to construct to a length of
4,280' but they would need to show the 95% length on the ALP and acquire
the land needed to extend to that length. As a result, significant
property acquisition would be required to shift, rotate, and extend the
runway to the south and establish the Runway OFA and RPZs on airport
property. Several residences, including one or two on the Wise
property, would need to be relocated to accommodate the shift, rotation,
and extension. Total reconstruction of the taxiways will be necessary
to accommodate the runway changes and meet design standards established
by the FAA. The FAA would participate in and support Option 3 if it was
planned to a length of 4,280'.
Fred and I met with Gary Gates at the MAD Conference in Missoula on
March 5th to discuss the Kalispell City Airport. The FAA presented
several key development criteria for Kalispell City Airport:
1. The FAA will not support planning or construction of an ARC B-I
facility at Kalispell City Airport. The current level of aviation
activity and projected forecasts require planning for a B-II facility
for FAA support.
2. The FAA would support planning for a runway length less than
100% (4,700') but not less than 95% (4,280'). The City would not
necessarily need to construct to a 95% length but would need to show
that length on the ALP and acquire the necessary land for a future
runway extension. The FAA prefers to leave the 100% length requirement
in the plan for now and allow the EA process to address length through
public comment.
3. The FAA would support additional planning to assess whether
there are other suitable runway orientations (between existing and the
proposed 5 degree rotation) that comply with FAA standards but minimize
the amount of land needed from the Wise family.
4. The FAA is not willing to compromise aviation needs in order to
fit the existing environment or conditions at the airport. In other
words, the FAA won't support an effort to determine what airport
facilities will work on land the airport currently owns or can easily
acquire (ie work around the Wise property).
In summary, the FAA will only support development at Kalispell City
Airport of a facility that meets B-II requirements and is planned for a
minimum runway length of 4,280 feet. Anything short of these
requirements will not be supported by the FAA. Options 1 and 2
therefore would not be eligible for any Federal funding or reimbursement
on past investment. Option 3 would be eligible for Federal funding and
reimbursement provided that the runway is planned to a length of 4,280'.
There is also the potential runway rotation less than 5 degrees that
would decrease the amount of land required from the Wise family and
still meet FAA design standards. The City may want to evaluate this
option further.
Please feel free to call me if you have any questions.
Thanks
Jeff Walla, PE
Stelling Engineers, Inc.
1372 Airport Road
Kalispell, MT 59901
phone: 406-755-8602
fax: 406-755-8710
email: jwalla@stellinginc.com <mailto:jwalla@jwalla@stellinginc.com>
慴楸慷൹猊灥牡瑡潩獩㤠✰䤠摡楤楴湯琠桴敳慰慲楴湯桴硥獩楴杮琠硡睩祡൳搊潮⁴敭瑥琠敨洠湩浩浵眠摩桴爠煥極敲敭瑮潦䝄䤭猠慴摮牡獤吠敨硥獩楴杮琠硡睩祡牡〲‧楷敤※䝄䤭猠慴摮牡獤爠煥極敲㈠✵眠摩琊硡睩祡†楄晦牥湥⁴灯楴湯牡潰獳扩敬琠潣獮牴捵⁴敮⁷慰慲汬汥慴楸慷獹琠慨⁴敭瑥䐠ⵇ⁉瑳湡慤摲†慅档漠瑰潩楷汬栠癡楤晦牥湥൴椊獳敵獡潳楣瑡摥眠瑩瑩䘠牯攠慸灭敬
晩愠摤瑩潩慮慬摮椠潮൴愊煣極敲湯琠敨眠獥⁴楳敤漠桴畲睮祡愠摮猠畯桴漠桴潣湮捥潴൲琊硡睩祡桴牥楷汬渠瑯戠畳晦捩敩瑮氠湡潴攠瑸湥桴慰慲汬汥慴楸慷⁹潴删湵慷⁹ㄳ吠獥慴汢獩桴敦獡扩汩瑩⁹景洠敥楴杮䐠ⵇ琊硡睩祡猠慴摮牡獤映牯愠汬漠桴灯楴湯楷汬爠煥極敲映牵桴牥癥污慵楴湯മ漊†倠牡⁴㜷䄠物灳捡桔畣牲湥⁴䱁⁐潤獥渠瑯椠据畬敤椠普牯慭楴湯漠൮倊牡⁴㜷愠物灳捡数
瑲楡楮杮琠桴硥獩楴杮爠湵慷⁹湡獩琠敨敲潦敲楤晦捩汵⁴潴攠慶畬瑡楷桴畯⁴楳湧晩捩湡⁴晥潦瑲匠浯慢楳ൣ漊獢牥慶楴湯牡桴瑡琠敨䬠䕇⁚慲楤潴敷獲愠敲瀠湥瑥慲楴湯潴琠敨畒睮祡㌠‱灡牰慯档猠牵慦散愠摮愠敲挠湯楳敤敲祢琠敨䘠䅁琠敢栠穡牡潤獵潴愠物渠癡杩瑡潩†桔牥污潳愠灰慥獲琠敢琠慲獮瑩潩慮畳晲捡㜨ㄺഩ瀊湥瑥慲楴湯祢琠敨䠠汩潴Ɱ删獯畡牥ⱳ愠摮䴠牵潤档†ഠ伊瑰潩‱畓
浭牡⁹潓敭瀠潲数瑲⁹捡畱獩瑩潩潷汵敢爠煥極敲潴獥慴汢獩桴畒睮祡传䅆漠楡灲牯⁴牰灯牥祴愠摮琠瑯污爠捥湯瑳畲瑣潩景桴慴楸慷獹眠汩敢渠捥獥慳祲琠潣灭祬眠瑩桴扡潳畬整洠湩浩浵敤楳湧猠慴摮牡獤攠瑳扡楬桳摥戠⁹桴䅆⹁†桔敷瑳猠摩慰慲汬汥琠硡睩祡潣汵潮⁴敢攠瑸湥敤潴琠敨攠摮漠畒睮祡㌠‱楷桴畯⁴摡楤楴湯污氠湡愊煣極楳楴湯䘠湩污祬桴獩漠瑰潩潷汵潮⁴敭瑥琠敨䘠
䅁猧洠湩浩浵删婐敲畱物浥湥獴吠敨䘠䅁眠畯摬渠瑯瀠牡楴楣慰整椠牯猠灵潰瑲传瑰潩റ猊湩散椠⁴潤獥渠瑯洠敥⁴ⵂ䥉搠獥杩瑳湡慤摲牯删婐爠煥極敲敭瑮ഠ伊瑰潩′潄丠瑯楨杮›䰠慥敶删湵慷⁹㌱㌭‱湩椠獴挠牵敲瑮氠捯瑡潩湡漊楲湥慴楴湯戠瑵猠楨瑦椠⁴潴琠敨猠畯桴琠敭瑥琠敨洠湩浩浵删婐敲畱物浥湥獴映牯删湵慷⁹㌱愠摮攠瑸湥潴愠氠湥瑧景㐠㈬〰⸧ഠ吊楨灯楴湯眠畯摬渠瑯洠敥⁴䅆⁁敤楳湧猠慴
摮牡獤映牯琠敨瀠潲敪瑣摥牣瑩捩污愠物牣晡⁴湡潷汵桴牥晥牯潮⁴敢攠楬楧汢潦湡⁹敆敤慲൬昊湵楤杮愠獳獩慴据†桔䅆⁁慨瑳瑡摥琠慨⁴桴祥眠汩潮⁴畳灰牯൴搊癥汥灯敭瑮漠湡䄠䍒䈠䤭映捡汩瑩⁹瑡琠敨䬠污獩数汬䌠瑩⁹楁灲牯†桔獩灯楴湯椠湩整摮摥琠敭瑥䐠獥杩片畯⁰⁉䐨ⵇ⥉猠慴摮牡獤愠摮椠൳琊敨敲潦敲猠浩汩牡琠灏楴湯ㄠ吠敨猠畯桴牥祬猠楨瑦愠摮攠瑸湥楳湯琠൯㐊㈬〰‧牡桴汥浥湥獴
琠慨⁴楤晦牥湥楴瑡瑩映潲灏楴湯ㄠ吠敨敲愠敲睴畳ⵢ慣整潧楲獥漠桴䝄䤭朠潲灵›浓污楁捲慲瑦䔠捸畬楳敶祬⠠䅓⥅湡潎⁴硅汣獵癩汥⁹浓污楁捲慲瑦⠠䕎䅓⸩†䅓⁅汰湡獥愠敲琠潨敳敷杩楨杮氠獥桴湡ㄠⰲ〵‰潰湵獤眠楨敬丠卅⁁汰湡獥愠敲琠潨敳眠楥桧湩൧洊牯桴湡ㄠⰲ〵㬰䐠獥杩片畯⁰⁉楡捲慲瑦愠敲瀠慬敮楷桴眠湩獧慰獮氠獥൳琊慨㤴⸧†桔潦汬睯湩獩愠戠楲晥猠浵慭祲漠桴獩畳獥愠摮琠敨
敦獡扩汩瑩⁹景洠敥楴杮䐠ⵇ⁉瑳湡慤摲楷桴爠獥数瑣琠潢桴匠䕁愠摮丠卅ു猊慴摮牡獤ഺ †畒睮祡ㄠⴳㄳⴠ䔠楸瑳湩畲睮祡眠摩桴漠〶‧敭瑥業楮畭楷瑤潦൲䐊ⵇ⁉潢桴匠䕁愠摮丠卅⹁†潃獮牴捵楴杮琠敬杮桴漠ⰴ〲✰眠瑩ൡ猊畯桴牥祬猠楨瑦漠〷✰眠汩敲畱物桴捡畱獩瑩潩景猠癥牥污潣浭牥楣污瀠潲数瑲敩牦湯楴杮唠⁓楈桧慷⁹㌹愠摮琠敨爠浥癯污漠敳敶慲൬戊極摬湩獧映潲桴獥牰灯牥楴
獥മ漊†删湵慷⁹扏敪瑣䘠敲牁慥ⴠ䄠琠瑯污眠摩桴漠㔲✰⠠㈱✵攠捡楳敤漠൦挊湥整汲湩⥥椠敲畱物摥映牯匠䕁※潴慴楷瑤景㐠〰‧㈨〰‧慥档猠摩漊散瑮牥楬敮
獩爠煥極敲潦䕎䅓䄠摤瑩潩慮慬摮愠摮挠敬牡湩潷汵戊敲畱物摥漠潢桴猠摩獥漠桴畲睮祡愠⁴桴潳瑵桴物景爠湵慷⁹潴潣灭祬眠瑩䅓⁅湡䕎䅓爠煥極敲敭瑮††畒睮祡倠潲整瑣潩潚敮桔獩爠煥極敲敭瑮椠潮⁴楤敲瑣祬爠汥瑡摥潴琠敨䐠獥杩片畯⁰畢⁴獩愠映湵瑣潩景琠敨䄠灰潲捡慃整潧祲⠠ⱁ䈠ബ攊捴⤮愠摮䄠灰潲捡楖楳楢楬祴䴠湩浩浵†桔業楮畭敲畱物浥湥⁴潦൲匊慭汬䄠物牣
晡⁴硅汣獵癩汥⁹湡楶畳污愠灰潲捡敨獩愠琠慲数潺摩污愠敲ൡ㈊〵‧⁸㔴✰砠ㄠ〬〰‧敢楧湮湩〲✰映潲慥档爠湵慷⁹湥吠敨挠牵敲瑮潬慣楴湯漠畒睮祡ㄠⴳㄳ搠敯潮⁴汰捡桴偒獚漠楡灲牯⁴牰灯牥祴愠൳琊敨䘠䅁眠畯摬爠煥極敲吠敭瑥琠楨敲畱物浥湥⁴潷汵敲畱物桳晩楴杮桴畲睮祡愠灰潲楸慭整祬㜠〰‧潴琠敨猠畯桴䄠摤瑩潩慮慬摮眠畯摬戠爊煥極敲潴琠敨猠畯桴映牯愠㜠〰‧桳晩⁴湡〶✰
攠瑸湥楳湯吠敨摡楤楴湯污氠湡敮摥摥眠畯摬椠据畬敤瀠牯楴湯景挠浯敭捲慩牰灯牥祴扡瑵楴杮唠⁓楈桧慷⁹㌹愠摮愠猠慭汬挠牯敮景琠敨瀠潲数瑲⁹睯敮祢琠敨楗敳映浡汩†慔楸慷獹ⴠ吠敨琠潷攠楸瑳湩慰慲汬汥琠硡睩祡牡潴汣獯潴畒睮祡ㄠⴳㄳ匠䕁猠慴摮牡獤爠煥極敲愠洠湩浩浵猠灥牡瑡潩景ㄠ〵ധ戊瑥敷湥瀠牡污敬慴楸慷獹愠摮爠湵慷獹※䕎䅓猠慴摮牡獤爠煥極敲愠洠湩浩浵景㈠㔲‧景猠灥牡
瑡潩†態楬灳汥楃祴䄠物潰瑲猧琠硡睩祡猠灥牡瑡潩獩湯祬㤠✰䤠摡楤楴湯琠桴敳慰慲楴湯桴硥獩楴杮琠硡睩祡潤渠瑯敭瑥琠敨洠湩浩浵眠摩桴爠煥極敲敭瑮潦䝄䤭猠慴摮牡獤吠敨攠楸瑳湩൧琊硡睩祡牡〲‧楷敤※䝄䤭猠慴摮牡獤⠠潂桴匠䕁愠摮丠卅⥁爠煥極敲㈠✵楷敤琠硡睩祡†瑉眠汩潮⁴敢瀠獯楳汢潴栠癡慰慲汬汥琠硡睩祡漠൮琊敨攠獡⁴楳敤漠桴畲睮祡琠慨⁴敭瑥䝄䤭丠卅⁁敲畱物浥
湥獴删獯畡牥൳椊潴汣獯潴琠敨攠楸瑳湩畲睮祡琠牰癯摩桴敳慰慲楴湯愠摮漠橢捥൴昊敲牡慥桴瑡愠敲爠煥極敲†瑉眠畯摬戠潰獳扩敬琠敭瑥䐠ⵇ⁉䅓猊慴摮牡獤潨敷敶†楄晦牥湥⁴灯楴湯牡潰獳扩敬琠潣獮牴捵⁴敮൷瀊牡污敬慴楸慷獹琠慨⁴敭瑥䐠ⵇ⁉䅓⁅瑳湡慤摲†慅档漠瑰潩楷汬栠癡搊晩敦敲瑮椠獳敵獡潳楣瑡摥眠瑩瑩吠獥慴汢獩桴敦獡扩汩瑩⁹景敭瑥湩䝄䤭匠䕁琠硡睩祡
猠慴摮牡獤眠汩敲畱物畦瑲敨癥污慵楴湯മ漊†倠牡⁴㜷䄠物灳捡桔畣牲湥⁴䱁⁐潤獥渠瑯椠据畬敤椠普牯慭楴湯漠൮倊牡⁴㜷愠物灳捡数瑲楡楮杮琠桴硥獩楴杮爠湵慷⁹湡獩琠敨敲潦敲楤晦捩汵⁴潴攠慶畬瑡楷桴畯⁴楳湧晩捩湡⁴晥潦瑲匠浯慢楳ൣ漊獢牥慶楴湯牡桴瑡琠敨䬠䕇⁚慲楤潴敷獲愠敲瀠湥瑥慲楴湯潴琠敨畒睮祡㌠‱灡牰慯档猠牵慦散愠摮愠敲挠湯楳敤敲祢琠敨䘠䅁琠敢栠穡牡潤獵潴愠物
渠癡杩瑡潩†桔牥污潳愠灰慥獲琠敢琠慲獮瑩潩慮畳晲捡㜨ㄺഩ瀊湥瑥慲楴湯祢琠敨䠠汩潴Ɱ删獯畡牥ⱳ愠摮䴠牵潤档†ഠ伊瑰潩′畓浭牡⁹楓湧晩捩湡⁴牰灯牥祴愠煣極楳楴湯眠畯摬戠敲畱物摥琠൯猊楨瑦愠摮攠瑸湥桴畲睮祡琠桴潳瑵湡獥慴汢獩桴畒睮祡传䅆漠൮愊物潰瑲瀠潲数瑲†敓敶慲畢楳敮獳獥映潲瑮湩单䠠杩睨祡㤠″潷汵敮摥潴戠敲潬慣整潴愠捣浯潭慤整琠敨猠楨瑦愠摮攠瑸湥楳
湯吠瑯污敲潣獮牴捵楴湯漠桴慴楸慷獹眠汩敢渠捥獥慳祲琠潣灭祬眠瑩桴愊獢汯瑵業楮畭敤楳湧猠慴摮牡獤攠瑳扡楬桳摥戠⁹桴䅆⹁†桔敷瑳猠摩瀊牡污敬慴楸慷⁹潣汵敢攠瑸湥敤潴琠敨攠摮漠畒睮祡㌠‱楷桴愠洠湩牯浡畯瑮漠摡楤楴湯污氠湡捡畱獩瑩潩†桔䅆⁁潷汵潮⁴慰瑲捩灩瑡湩牯猠灵潰瑲传瑰潩′楳据瑩搠敯潮⁴敭瑥䈠䤭⁉敤楳湧猠慴摮牡獤മ ഠ伊瑰潩″敒潣獮牴捵⁴
桴畲睮祡琠ⵂ䥉猠慴摮牡獤愠潬杮愠ㄠⴴ㈳牯敩瑮瑡潩潴愠氠湥瑧景㌠㜬〰⸧ഠ吊敨䘠䅁眠畯摬猠灵潰瑲琠敨瀠慬湮湩湡潣獮牴捵楴湯漠桴敮⁷畲睮祡琠൯䐊ⵇ䥉猠慴摮牡獤戠瑵眠畯摬渠瑯猠灵潰瑲愠爠湵慷⁹敬杮桴氠浩瑩摥琠ⰳ〷✰മ吊敨䘠䅁栠獡椠摮捩瑡摥琠慨⁴桴祥眠汩畳灰牯⁴汰湡楮杮漠敬杮桴漠൦㐊㈬〸‧桷捩潷汵捡潣浭摯瑡㔹‥景琠敨䜠⁁汦敥㭴瀠慬湮湩潴琠敨汵楴慭整氠湥瑧潦〱┰漠
桴䅇映敬瑥眠畯摬渠瑯戠敲畱物摥映牯䘠䅁畳灰牯†楓据業楮畭畲睮祡氠湥瑧景㐠㈬〸‧潷汵敢爠煥極敲潦൲䘊䅁猠灵潰瑲桴獩畳獥瀠牥慴湩湩潴琠楨灯楴湯楷汬戠牰獥湥整湩桴瑡挠湯整瑸吠楨獩攠獳湥楴污祬琠敨漠瑰潩桳睯湯琠敨挠牵敲瑮䄠偌畢⁴〵✰猠潨瑲牥吠敨映汯潬楷杮椠牢敩畳浭牡⁹景琠敨椠獳敵湡琊敨映慥楳楢楬祴漠敭瑥湩䝄䤭⁉瑳湡慤摲湯愠爠瑯瑡摥漠歳睥摥
污杩浮湥⁴湡敬杮桴漠ⰴ㠲✰ഺ †畒睮祡ㄠⴴ㈳ⴠ丠睥爠湵慷⁹獩挠湯瑳畲瑣摥琠楷瑤景㜠✵琠敭瑥䝄䤭⁉瑳湡慤摲†獁渠瑯摥愠潢敶桴䅆⁁潷汵敲畱物汰湡楮杮琠ൡ氊湥瑧桴瑡愠捣浯潭慤整㔹‥景琠敨䜠⁁汦敥⁴牯㐠㈬〸⸧†畓獢慴瑮慩൬氊湡捡畱獩瑩潩潷汵敢爠煥極敲潦桴潲慴整污杩浮湥ⱴ猠畯桴牥祬桳晩ⱴ愠摮攠瑸湥楳湯琠ⰴ㠲✰䄠汬漠桴敮⁷牰灯牥祴愠煣極楳楴湯桳
睯湯琠敨挠牵敲瑮䔠桸扩瑩䄠倠潲数瑲⁹慍⁰潷汵敢爠煥極敲†潈敷敶Ⱳ敃敭整祲删慯潷汵潮⁴敮摥琠敢爠汥捯瑡摥†畒睮祡传橢捥⁴牆敥䄠敲⁁潴慴楷瑤景㔠〰‧㈨〵‧慥档猠摩景散瑮牥楬敮
獩爠煥極敲潦䝄䤭⁉瑳湡慤摲†汁景琠敨渠睥瀠潲数瑲൹愊煣極楳楴湯猠潨湷漠桴畣牲湥⁴硅楨楢⁴⁁牐灯牥祴䴠灡眠畯摬戠爊煥極敲潴瀠潲整瑣琠敨传䅆ഠ漊†删湵慷⁹牐瑯捥楴湯娠湯獥ⴠ吠楨敲畱物浥湥⁴獩渠瑯搠物捥汴⁹敲慬整琊桴敄楳湧䜠潲灵戠瑵椠畦据楴湯漠桴灁牰慯档䌠瑡来牯⁹䄨ⱂ瑥
湡灁牰慯档嘠獩扩汩瑩⁹楍楮畭獭吠敨爠煥極敲敭瑮映牯䄠物牣晡൴䄊灰潲捡慃整潧楲獥䄠愠摮䈠眠瑩楶畳污愠灰潲捡敨漨偎⁉潮⁴潬敷൲琊慨‱業敬
獩愠琠慲数潺摩污愠敲〵✰砠㜠〰‧⁸ⰱ〰✰戠来湩楮杮㈠〰ധ昊潲慥档爠湵慷⁹湥吠敨瀠潲潰敳潬慣楴湯漠畒睮祡ㄠⴴ㈳⠠獡猠潨湷漠൮琊敨䄠偌
潷汵汰捡桴畒睮祡ㄠ‴偒⁚湯愠物潰瑲瀠潲数瑲㭹琠敨删湵慷൹㌊′偒⁚潷汵敲畱物慬摮愠煣極楳楴湯琠潣灭祬眠瑩䅆⁁敲畱物浥湥獴ഠ漊†吠硡睩祡桔獩漠瑰潩汰湡潦桴敲潣獮牴捵楴湯漠桴慴楸慷獹潴䐠ⵇ䥉猠慴摮牡獤吠敨瀠潲潰敳慬摮愠煣極楳楴湯椠据畬敤桴牰灯牥祴敮散獳牡⁹潴挠湯瑳畲瑣琠敨渠睥琠硡睩祡桴瑡挠浯汰⁹楷桴䘠䅁搠獥杩൮猊慴摮牡獤മ漊†倠牡⁴㜷䄠物灳捡桔獩漠瑰潩
業楮業敺扯瑳畲瑣潩獮琠桴慐瑲㜠ഷ愊物灳捡牣慥整祢猠牴捵畴敲牦湯楴杮唠⁓楈桧慷⁹㌹吠敨䘠䅁眠汩൬猊楴汬爠煥極敲琠慨⁴桴䝋婅爠摡潩琠睯牥敢爠浥癯摥戠晥牯桴祥眠汩൬猊灵潰瑲椠灭潲敶敭瑮瑡䬠污獩数汬䌠瑩⁹楁灲牯ഠ伊瑰潩″畓浭牡⁹桔獩漠瑰潩楷汬漠汮⁹慧湲牥䘠䅁猠灵潰瑲椠桴瀊慬湮摥氠湥瑧景删湵慷⁹㐱㌭′獩㐠㈬〸‧潴愠捣浯潭慤整㤠┵漠桴䅇汦敥†桔楃祴眠畯摬渠瑯
渠捥獥慳楲祬渠敥潴挠湯瑳畲瑣琠敬杮桴漠൦㐊㈬〸‧畢⁴桴祥眠畯摬渠敥潴猠潨⁷桴㔹‥敬杮桴漠桴䱁⁐湡捡畱物琊敨氠湡敮摥摥琠硥整摮琠桴瑡氠湥瑧†獁愠爠獥汵ⱴ猠杩楮楦慣瑮牰灯牥祴愠煣極楳楴湯眠畯摬戠敲畱物摥琠桳晩ⱴ爠瑯瑡ⱥ愠摮攠瑸湥桴爊湵慷⁹潴琠敨猠畯桴愠摮攠瑳扡楬桳琠敨删湵慷⁹䙏⁁湡偒獚漠楡灲牯൴瀊潲数瑲†敓敶慲敲楳敤据獥湩汣摵湩湯牯琠潷漠桴楗敳
牰灯牥祴潷汵敮摥琠敢爠汥捯瑡摥琠捡潣浭摯瑡桴桳晩ⱴ爠瑯瑡潩Ɱ湡硥整獮潩†潔慴敲潣獮牴捵楴湯漠桴慴楸慷獹眠汩敢渠捥獥慳祲潴愠捣浯潭慤整琠敨爠湵慷⁹档湡敧湡敭瑥搠獥杩瑳湡慤摲獥慴汢獩敨戊⁹桴䅆⹁†桔䅆⁁潷汵慰瑲捩灩瑡湩愠摮猠灵潰瑲传瑰潩″晩椠⁴慷൳瀊慬湮摥琠敬杮桴漠ⰴ㠲✰മ 牆摥愠摮䤠洠瑥眠瑩慇祲䜠瑡獥愠⁴桴䅍⁄潃普牥湥散椠楍獳畯慬漠൮䴊
牡档㔠桴琠楤捳獵桴態楬灳汥楃祴䄠物潰瑲吠敨䘠䅁瀠敲敳瑮摥敳敶慲敫⁹敤敶潬浰湥⁴牣瑩牥慩映牯䬠污獩数汬䌠瑩⁹楁灲牯㩴ഠ ⸱吉敨䘠䅁眠汩潮⁴畳灰牯⁴汰湡楮杮漠潣獮牴捵楴湯漠湡䄠䍒䈠䤭慦楣楬祴愠⁴態楬灳汥楃祴䄠物潰瑲吠敨挠牵敲瑮氠癥汥漠癡慩楴湯捡楴楶祴愠摮瀠潲敪瑣摥映牯捥獡獴爠煥極敲瀠慬湮湩潦ⵂ䥉映捡汩瑩൹昊牯䘠䅁猠灵潰瑲മ ⸲吉敨䘠䅁眠畯摬猠灵潰瑲瀠慬湮湩潦
畲睮祡氠湥瑧敬獳琠慨൮ㄊ〰‥㐨㜬〰⤧戠瑵渠瑯氠獥桴湡㤠┵⠠ⰴ㠲✰⸩†桔楃祴眠畯摬渠瑯敮散獳牡汩⁹敮摥琠潣獮牴捵⁴潴愠㤠┵氠湥瑧畢⁴潷汵敮摥琠桳睯桴瑡氠湥瑧湯琠敨䄠偌愠摮愠煣極敲琠敨渠捥獥慳祲氠湡潦畦畴敲畲睮祡攠瑸湥楳湯吠敨䘠䅁瀠敲敦獲琠敬癡桴〱┰氠湥瑧敲畱物浥湥൴椊桴汰湡映牯渠睯愠摮愠汬睯琠敨䔠⁁牰捯獥潴愠摤敲獳氠湥瑧桴潲杵൨瀊扵楬潣浭湥ഠ
㌊म桔䅆⁁潷汵畳灰牯⁴摡楤楴湯污瀠慬湮湩潴愠獳獥桷瑥敨൲琊敨敲愠敲漠桴牥猠極慴汢畲睮祡漠楲湥慴楴湯戨瑥敷湥攠楸瑳湩湡桴瀊潲潰敳‵敤牧敥爠瑯瑡潩⥮琠慨⁴潣灭祬眠瑩䅆⁁瑳湡慤摲畢⁴業楮業敺桴浡畯瑮漠慬摮渠敥敤牦浯琠敨圠獩慦業祬മ ⸴吉敨䘠䅁椠潮⁴楷汬湩潴挠浯牰浯獩癡慩楴湯渠敥獤椠牯敤潴楦⁴桴硥獩楴杮攠癮物湯敭瑮漠潣摮瑩潩獮愠⁴桴楡灲牯†湉漠桴牥
潷摲ⱳ琠敨䘠䅁眠湯琧猠灵潰瑲愠晥潦瑲琠敤整浲湩桷瑡愠物潰瑲慦楣楬楴獥眠汩潷歲漠慬摮琠敨愠物潰瑲挠牵敲瑮祬漠湷牯挠湡攠獡汩൹愊煣極敲⠠敩眠牯牡畯摮琠敨圠獩牰灯牥祴⸩†ഠ䤊畳浭牡ⱹ琠敨䘠䅁眠汩湯祬猠灵潰瑲搠癥汥灯敭瑮愠⁴態楬灳汥楃祴楁灲牯⁴景愠映捡汩瑩⁹桴瑡洠敥獴䈠䤭⁉敲畱物浥湥獴愠摮椠汰湡敮潦ൡ洊湩浩浵爠湵慷⁹敬杮桴漠ⰴ㠲‰敦瑥䄠祮桴湩桳牯⁴景琠敨敳敲畱
物浥湥獴眠汩潮⁴敢猠灵潰瑲摥戠⁹桴䅆⹁†灏楴湯‱湡ല琊敨敲潦敲眠畯摬渠瑯戠汥杩扩敬映牯愠祮䘠摥牥污映湵楤杮漠敲浩畢獲浥湥൴漊慰瑳椠癮獥浴湥†灏楴湯㌠眠畯摬戠汥杩扩敬映牯䘠摥牥污映湵楤杮愠摮敲浩畢獲浥湥⁴牰癯摩摥琠慨⁴桴畲睮祡椠汰湡敮潴愠氠湥瑧景㐠㈬〸⸧桔牥獩愠獬桴潰整瑮慩畲睮祡爠瑯瑡潩敬獳琠慨‵敤牧敥桴瑡潷汵敤牣慥敳琠敨愠潭湵⁴景氠湡敲畱物摥映潲
桴楗敳映浡汩⁹湡猊楴汬洠敥⁴䅆⁁敤楳湧猠慴摮牡獤吠敨䌠瑩⁹慭⁹慷瑮琠癥污慵整琠楨൳漊瑰潩畦瑲敨ഠ倊敬獡敦汥映敲潴挠污敭椠潹⁵慨敶愠祮焠敵瑳潩獮മ 桔湡獫ഠ䨊晥慗汬ⱡ倠匊整汬湩湅楧敮牥ⱳ䤠据മㄊ㜳′楁灲牯⁴潒摡態楬灳汥ⱬ䴠⁔㤵〹റ瀊潨敮›㐠㘰㜭㔵㠭〶ല昊硡›㐠㘰㜭㔵㠭ㄷര攊慭汩›樠慷汬䁡瑳汥楬杮湩潣洼楡瑬㩯睪污慬橀慷汬䁡瑳汥楬杮湩潣㹭†ഠ