Вы находитесь на странице: 1из 39

Aviation Environmental Design Tool

AEDT Release Notes


Release AEDT 2d Update 1
Release Date: February 12, 2018
Revision: 93.1.7128.1
Database Revisions:
• AIRPORT v2.16.3
• FLEET v3.24.4
• STUDY v1.54.2
Installer Size:
• Install AEDT 2d.exe: 992 MB
• Install AEDT 2d Distributed Processing.exe: 357 MB

Instructions on how to install AEDT can be found in Section 5.2 of the Installation Guide.

Resolved Issue
This AEDT 2d Update 1 includes the Esri patch for the following issue that affected AEDT installed on
Microsoft Windows 7 and Windows 2008 R2 machines.
• Microsoft Windows Security Updates (KB4056894 and KB4056897) caused the Esri
geoprocessing services to fail on Windows 7 or Windows 2008 R2 computers. As a result, AEDT
functionality which uses Esri geoprocessing services also failed (e.g., generating noise contour,
pollutant concentration contour, population exposure report, Environmental Justice boundary,
and exporting a map layer as shapefile).

AEDT software and databases in the AEDT 2d Update 1 (93.1.7128.1) remain the same as the AEDT 2d
release (93.0.6136.1). The only change is the Esri DLL file, DADFLib.dll, which gets installed by AEDT
(under C:\Program Files\FAA\AEDT\ArcGISRuntime10.2.5\LocalServer64\bin).

For further information on the Esri patch, please refer to:


• https://support.esri.com/en/download/7580
• https://blogs.esri.com/esri/arcgis/2018/01/23/software-patches-released-for-arcgis-server-
geoprocessing-service-issue/

1
Aviation Environmental Design Tool
Release AEDT 2d
Release Date: September 27, 2017
Revision: 93.0.6136.1
Database Revisions:
• AIRPORT v2.16.3
• FLEET v3.24.4
• STUDY v1.54.2
Installer Size:
• Install AEDT 2d.exe: 992 MB
• Install AEDT 2d Distributed Processing.exe: 357 MB

This AEDT 2d release includes new features, updates, and bug fixes. A full list of updates and bug fixes is
listed below.

Instructions on how to install AEDT can be found in Section 5.2 of the Installation Guide.

The support for Microsoft SQL Server 2008 R2 ended with the AEDT 2d release. The
supported Microsoft SQL Server version for AEDT 2d is Microsoft SQL Server 2012.
Microsoft SQL Server 2012 must be installed prior to installing AEDT 2d.

New and Updated Features


1. Dynamic grid support for time-based noise metrics
• Implemented dynamic grid for time above metrics (TALA, TALC, TAPNL) and time audible
metrics (TAUD, TAUDP, TAUDSC, TAUDPSC)
2. MOVES Links
• Added ability to create roadway, parking facility, and construction zone features in the
airport layout designer.
• Added ability to edit the properties of roadway, parking facility, and construction zone.
• Implemented the ability to export the MOVES links features in the MOVES links format.
3. MOVES inventory file improvement
• Added ability to import MOVES links file.
• Added ability to import more than one MOVES inventory & links file and create MOVES
inventory scenarios.
• Added ability to assign MOVES inventory scenario(s) to Emissions/Emissions Dispersion
metric result.
4. VALE Report improvement
• Implemented support for the MOVES sources (roadway, parking, and construction).
5. Define Metric Results wizard improvement
• Added ability to specify name and description for metric results.
• Added ability to specify weather for metric results (this used to be a study-wide setting)
6. Migrate Studies feature
• Implemented the Migrate Studies dialog which copies AEDT studies from a SQL Server 2008
R2 instance to a SQL Server 2012 instance.
7. Create and edit vector tracks in Airport tab
• Added ability to create departure, approach, and TGO vector tracks
• Moved the floating Airport Layout Designer tool bar to the Designer tab
• Moved the Edit Track dialog to the Designer tab, right-hand pane
2
Aviation Environmental Design Tool
8. Track dispersion enhancements in Airports tab
• Added ability to edit dispersed tracks graphically on the map by dragging the backbone track
• Added ability to edit dispersed tracks in the Edit Track pane where the number of subtracks
and subtrack spacings can be changed
9. Metric Results Import and Combine feature improvement
• Added ability to import multiple .grd files at the same time.
• Added ability to combine acoustic metric results with different receptor sets
• Implemented the union and intersection combine methods
• Added support for generating noise contours for point-type receptor sets
10. High Fidelity Weather Implementation of MERRA-2 and WRF
• Implemented support for MERRA-2 and WRF weather for aircraft performance, fuel burn,
and emissions modeling
• Added the NC4WXEditorWPF.exe application for pre-processing MERRA-2 and WRF raw
weather data
11. Sensor Path Import (SPI) tool
• Added the SPI.exe command-line application for importing sensor path data into AEDT study
12. User-defined aircraft improvement in Equipment tab, Aircraft
• Added ability to edit the ANP profile weight of a new user-defined aircraft in Equipment tab,
Aircraft screen.
13. Study Database Update to version 1.54.2
14. Fleet Database Update to version 3.24.4
• New Airframes and ACCODES – 50 new airframes were added. These records were derived
from updates to [FLEET].[dbo].[FLT_FLEET]. New airframes are those having Airframe_ID >
5413 in [FLEET].[dbo].[FLT_AIRFRAMES].
o Note: [FLEET].[dbo].[FLT_FLEET] is a global registry of active, fixed wing aircraft which
was recently update to include aircraft through December 31, 2015. FLT_FLEET is not
populated in the public release of AEDT.
• Engine Location – Engine location fixed for five airframes in [FLEET].[dbo].[FLT_AIRFRAMES]
o AIRFRAME_ID  4585, 4832, 5010, 5357, 5401
• ICAO Emissions Databank (EDB) v.23c – The [FLEET].[dbo].[FLT_ENGINES] table has been
updated with data from the ICAO EDB v. 23c. Engines marked as ‘superseded’ in the EDB
have been added as new records in [FLEET].[dbo].[FLT_ENGINES]. The superseded
designation may reflect a physical update to manufactured engines or an update to the
measured data provided by the manufacturer for an engine that is already available. New
engines are those having ENGINE_ID > 1992 in [FLEET].[dbo].[FLT_ENGINES]
o Note: The ICAO EDB model of superseding engines allows for engine models to have
multiple engine codes which may have different engine data. The most recently
updated engine code for a given model will have a ‘NULL’ value in the superseded
column of [FLEET].[dbo].[FLT_ENGINES]
• New Equipment – 482 new records have been added to [FLEET].[dbo].[FLT_EQUIPMENT].
New equipment are those having EQUIP_ID > 4630. New equipment records are a result of
new combinations of airframe_id, engine_id, and engine_mod_id which were derived from
updates to FLT_FLEET.
• BADA 3.13.1 – Addition of the A350-900 having BADA_ID = ‘A359’
• Equipment Update for Bugs 961 and 2285 – ANP_Airplane_IDs for Equipment with A350
airframes have been remapped from ‘A340-211’ to ‘A330-343’. Engine IDs have been
assigned to ENGINE_ID = 1988 (Tent 772). Note that Equipment_ID = 3497 has been

3
Aviation Environmental Design Tool
replaced by Equipment_ID = 4809 and Equipment_ID = 4246 has been replaced by
Equipment_ID = 5308. See below for a detailed table of all ANP remappings.
• New ANP Aircraft – Three new ANP aircraft have been added to the FLEET database:
o 7378MAX
 EQUIP_ID  4128, 4129
o BD-700-1A10 (Global Express 6000)
 EQUIP_ID  1773, 1774, 1775, 1776, 1777, 1778, 1779, 1780, 1783, 3733, 3734,
4197, 5354, 5355
o BD-700-1A11 (Global Express 5000)
 EQUIP_ID  2573, 3731, 3732
• ANP Remapping – The ANP_AIRPLANE_ID column in [FLEET].[dbo].[FLT_EQUIPMENT] was re-
assigned for 76 records in [FLEET].[dbo].[FLT_EQUIPMENT]. Revisions to ANP assignments are
implemented to achieve a more balanced and accurate mapping for noise and performance
modelling. The following table lists the 76 equipment with remapped ANP ID.

ENGINE_ ANP_AIRPLANE_ID
EQUIP_ID AIRFRAME_ID ENGINE_ID BADA_ID
MOD_ID AEDT 2c AEDT 2d
65 4557 1338 140 707320 74720B A345
91 4584 1258 140 720B 727EM1 B703
92 4584 1262 140 720B 727EM1 B703
127 4587 1263 140 737 737N17 B732
129 4587 1264 97 737 737N17 B732
133 4587 1261 140 737 737N17 B732
138 4587 1268 140 737D17 737N17 B732
1187 4840 1531 140 LEAR25 LEAR35 FA50
1318 4784 1205 140 COMJET CNA750 FA50
1319 4785 1205 140 COMJET CNA750 FA50
1330 4703 1462 140 CVR580 DHC830 DH8C
1331 4703 1463 140 CVR580 DHC830 DH8C
1332 4703 1461 140 CVR580 DHC830 DH8C
1393 4714 1260 140 DC860 DC870 DC87
1410 4716 1265 140 DC910 DC93LW DC94
1420 4718 1265 140 DC9Q9 DC95HW DC94
1705 4732 1665 140 CVR580 DHC830 DH8D
1773 4793 1432 140 GV BD-700-1A10 GL5T
1774 4793 1433 140 GV BD-700-1A10 GL5T
1775 4793 1435 140 GV BD-700-1A10 GL5T
1776 4793 1434 140 GV BD-700-1A10 GL5T
1777 4793 1438 140 GV BD-700-1A10 GL5T
1778 4793 1437 140 GV BD-700-1A10 GL5T
1779 4793 1436 140 GV BD-700-1A10 GL5T
1780 4793 1439 140 GV BD-700-1A10 GL5T
1783 4793 1377 140 GV BD-700-1A10 GL5T
1824 4910 1549 140 F16PW9 F16PW0 FGTN
2013 4815 1205 140 FAL20 LEAR35 H25A
2014 4816 1205 140 FAL20 LEAR35 FA20
2023 4638 1292 140 LEAR25 MU3001 BE40
2024 4638 1294 140 CNA500 MU3001 BE40
2439 5059 1509 140 COMJET CNA750 FA7X
2573 5071 1439 140 GV BD-700-1A11 GLEX
3035 4638 1295 140 LEAR25 MU3001 BE40
3089 4784 1714 140 COMJET CNA750 FA50
3090 4785 1714 140 COMJET CNA750 FA50
3104 4815 1714 140 FAL20 LEAR35 H25A

4
Aviation Environmental Design Tool
3105 4816 1714 140 FAL20 LEAR35 FA20
3168 4587 1264 98 737QN 737N17 B732
3169 4598 1283 140 747100 74710Q B742
3199 4841 1205 136 C140 LEAR35 FA50
3208 4810 1714 50 DOMIN LEAR35 H25A
3210 4599 1412 131 E4 747200 B742
3231 4706 1409 53 KC10A DC1010 DC10
3249 4589 1210 54 T-43A 737N17 B733
3264 4557 1282 140 707320 74720B A345
3498 5027 1988 140 A340-211 A330-343 A359
3731 5071 1439 145 GV BD-700-1A11 GLEX
3732 5071 1439 261 GV BD-700-1A11 GLEX
3733 4793 1439 145 GV BD-700-1A10 GL5T
3734 4793 1439 261 GV BD-700-1A10 GL5T
3743 4815 1849 140 IA1125 LEAR35 FA20
3744 4816 1849 140 IA1125 LEAR35 FA20
3745 5075 1849 140 IA1125 LEAR35 FA20
3930 5203 1261 140 DC950 DC95HW DC94
3931 5203 1262 140 DC950 DC95HW DC94
3932 5203 1263 140 DC950 DC95HW DC94
3933 5203 1264 140 DC950 DC95HW DC94
3934 5203 1265 140 DC9Q9 DC95HW DC94
3937 5203 1268 140 DC950 DC95HW DC94
3942 5203 1273 140 DC950 DC95HW DC94
3943 5203 1274 140 DC950 DC95HW DC94
3944 5203 1275 140 DC950 DC95HW DC94
3945 5203 1276 140 DC950 DC95HW DC94
3946 5203 1452 140 DC950 DC95HW DC94
3947 5203 1453 140 DC950 DC95HW DC94
3948 5203 1454 140 DC950 DC95HW DC94
3949 5203 1455 140 DC950 DC95HW DC94
3950 5203 1772 140 DC950 DC95HW DC94
4128 5335 2003 140 737700 7378MAX B737
4129 5336 2003 140 737800 7378MAX B738
4197 5355 1439 140 GV BD-700-1A10 FA7X
4221 4584 1260 140 720 727EM1 B703
4401 5400 1665 140 CVR580 DHC830 DH8D
3497  5028 1988 140 A340-211 A330-343 A359
4809
4246  5378 1988 140 A340-211 A330-343 A359
5308

Resolved Issues
ID Description
4295 Fix Incorrect Engine Locations in FLT_AIRFRAMES
4294 Remap A350 airframes to A330 ANPs (currently A340 ANPs) in FLT_Equipment
4241 Logview on GUI sometimes cause uncaught exception
4219 "Object Reference" error during ASIF import if APU in ASIF file is invalid
4214 Fix FLT_ANP_BADA_ENERGYSHARE with valid combinations from FLT_EQUIPMENT
4213 "Run until AERMOD" metric result is displayed with wrong icon after AEDT restart
4209 Remove range validation from default contour min/max fields in Study Preferences
4194 Progress bar % text is incorrect if runups are included
4134 AERMOD hang if there is no weather data

5
Aviation Environmental Design Tool
4074 Modify the ASIF Importer to parse the two taxi time fields from the airportLayout element and
populate the corresponding fields in the AIRPORT_LAYOUT table
4072 Modify the EDMS2ASIF converter to write out the totalTaxiTimeIn and totalTaxiTimeOut
underneath the airportLayout element
4071 Update ASIF schema to remove taxi time elements from the case element and add taxi time
elements to the airportLayout element
4010 Receptor set layer for time audible metrics is not rendered correctly
3994 Resolve additional detailed noise issues
3973 Noise results are empty for Maximum Level user-defined noise metrics
3971 Edit operations feature resets GSE durations
3886 Data input in Study Boundary dialog is not user-friendly
3859 “Save interim results…” is not checked, AEDT won't serialize aggregated dictionary
3836 Verify SQL server is reachable during install upgrade
3821 Application crash when generating emissions dispersion contours
3820 Imported INM study show current date for scenario and case in Annualization window
3819 Verify upgrade from SP1 to SP2 or SP2 to SP3 with custom install & data folders
3816 Add missing SPECT_AFB data to FLT_ANP_AIRPLANE_NOISE_GROUPS for CNA182, CNA208,
DO228, DO328, PA42
3810 Upgrading AEDT results in mislabeled desktop icon
3809 Uninstalling AEDT leaves non-functional shortcut on desktop
3805 Paused metric is displayed with wrong icon
3789 Metric result progress bar is 100%, but the job is still in progress
3786 Study Name with Spaces
3784 Remove "Physical Map" from the list of basemaps
3783 Upgrading from SP1 to SP2 corrupts installation if user specified custom install folder
3772 Noise metric status is displayed during circle boundary operation
3763 installation fails when only the databases are selected in Custom Setup
3758 Installing both SP1 and SP2 can cause conflict
3737 Fix messages when SQL server instance is in use
3717 Incorrect run options
3704 Several FAA.AEE.AEDT dlls do not have the latest file version numbers
3699 Run options are missing from metric results pullright menu
3698 The icons on the metric results Run ribbon dropdown are all the same
3676 Import of INM study with no runways fails
3675 Import of INM study neglects user-defined fixed-point overflight
3673 AAM ignores bank angle
3646 In Definitions tab, hide controls when no Metrics entry is selected
3644 Import fails for simple functioning INM study with user-defined airport
3634 Hide controls when no MOVES AERMOD Files entry is selected
3628 Null ReceptorArea property in receptor set layer causes crash
3586 Incorrect partial import of track nodes
3467 Improve usability of the panes underneath the Definitions tab
3404 Detailed grids do not correctly compute user defined non-exposure metrics
3233 Edit Runway End dialog have required fields that aren't required
3216 investigate problem with C-weighted metrics for propeller-driven aircraft
3115 Status of emissions dispersions run is set to completed before it is complete
4768 Increase max number of roadway link segments to 100
4318 ASIF Import INM study assigned wrong Operation Times
4786 Attempting to import binary-encoded GRD causes system hang
6
Aviation Environmental Design Tool
4685 Resolve bug for User Value and User Cutback Thrust
4751 Disable the hi-fi weather & study boundary warning when running metric result
4539 EDMS and AEDT use incorrect CO emissions factor for emergency generator – Type 1
4634 THC, VOC, and NMHC factors for Gasoline Emergency Generator in AEDT are different vs. EDMS

Known Issues
1. Uninstalling AEDT when another application is connected to the AEDT databases leaves any
connected databases on the server. As a workaround, delete the databases manually using
Microsoft SQL Server Management Studio. (12194)
2. After closing a study in the AEDT application, Microsoft SQL Server still maintains a connection to
the database for several minutes. To delete a study database, exit from the AEDT application first;
then delete the desired database in the Microsoft SQL Server Management Studio. (18027)
3. User settings from prior installations may not be removed exhibiting behavior such as failed contour
generation (old filename for contouring gpk). Manually delete the file C:\AEDT\DATA\[User
name]\user_settings.json where [User name] is the Windows account name under which the user is
working.
4. “Unable to upgrade study” error will be displayed during the study upgrade process if a study
contains a non-aircraft equipment group. Delete the non-aircraft equipment groups from a study
before upgrading it. (22077)
5. Aircraft equipment groups cannot be used to assign tracks to operations. User’s only access to
Operation Group Percent Distribution processing is through direct SQL injection of AIR_OPERATION
table. (1731)
6. Flight profiles are not editable when creating a user-defined aircraft in Equipment tab. Use ASIF
import in order to create a new aircraft with different flight profiles. (21323)
7. Deleting user-defined helicopter is not supported in the Equipment tab. (669)
8. Opening multiple emissions reports may show data from a different report. To avoid this issue, open
only one emissions report at a time. (21322)
9. In the Speciated Organic Gases tab in the Emissions Report, repeatedly converting units may
produce inconsistent values in the report. (21329)
10. If you get a “timeout expired” error when generating an emissions report, a workaround is to:
1) In Study tab, Database Preferences, increase the “Datacontext timeout” setting (e.g. 300
seconds).
2) Generate the “Operation Summary” emissions report first.
3) Generate the “Operation Group Summary” emission report.
11. Some airframe/engine combinations from EDMS 5.1.4.1 system data are incongruent with AEDT and
are reported “bad data integrity” errors during EDMS study import. To correct, import the aircraft as
user-defined aircraft. (21179)
12. When an EDMS study containing grid receptor sets is converted to AEDT, the rendering of receptor
locations will be slightly mismatched between EDMS and AEDT. This is because in AEDT the origin of
the grid receptor is in the south-west corner, while EDMS uses the offsets based on the center of the
grid. A workaround is to:
1) Incorporate the grid and the discrete receptors in the EDMS study into an AERMOD.INC file.
7
Aviation Environmental Design Tool
2) In AEDT, go to Study tab, Preferences, Emissions Dispersion.
3) Check the “Use AERMOD receptor grid” option and reference the .INC file from step 1 in the
“File with AERMOD receptor grid” option. This makes the application ignore the receptor set
assigned to the emissions dispersion metric result, and forces using the specified AERMOD grid
receptor. The INC file can contain both grid and discrete receptors.
13. The INM to ASIF Converter does not convert system aircraft with user modified properties (i.e.
added a custom profile, but still used the same system aircraft name). A workaround is to rename
the aircraft with a unique name so that the Converter recognizes it as a user-defined aircraft.
14. The INM to ASIF Converter does not convert user-defined helicopters and user-defined military
aircraft in an INM study. (942)
15. Airports with an expiration date set to a past date may not import via ASIF. A workaround is to
change the expiration date in the Airports database.
16. A helitaxi track imported via ASIF will be listed in the Airports Details pane, however it will not be
displayed on the map as part of the airport layout layer. To view the helitaxi track on map, view
tracks in the Metric Results tab. (21029)
17. After a partial ASIF import, the application does not refresh. Restart the application to view the
imported data. (671)
18. Weather import does not take into account Airport Layout Start date. Manually confirm that the
dates for weather data being used are after the start date of the associated airport layout. (8386)
19. Processing of high fidelity weather data is not thread-safe. To compensate, set the
“NumberOfThreads” key to 1 in C:\Program
Files\FAA\AEDT\FAA.AEE.AEDT.GUI.View.Ribbon.exe.config file. (21287)
20. Flight operations specifying cruise altitude above the highest allowable specified aircraft altitude are
processed. Manually confirm cruise altitude on the operation against the BADA cruise altitude limit.
(6676)
21. AEDT is unable to process 3CD terrain files. A workaround is to use GridFloat files instead. (929)
22. An AEDT generated shapefile cannot be imported into Google Earth Pro. (21979)
23. Noise contours may be displaced on the map (i.e. does not align with the receptor set) if the X and Y
spacings are not the same. (22072)
24. When applying Delay & Sequencing, air operations based on operational profiles with “Operation
Count” values that are small, e.g. less than one operation per scenario duration, are subject to a
quantization error in the assignment of the operation time.
25. Emissions dispersion metric results created in previous AEDT version (e.g., AEDT 2c or AEDT 2b)
cannot be run in AEDT 2c SP1. A workaround is to copy the existing dispersion metric result and
create a new one. (3237)
26. Dispersed tracks are not supported for emissions dispersion modeling.
27. On a low resolution computer screen, the bottom portion of the Edit Operations wizard cannot be
accessed. (3113)
28. In order to generate results for vertical fuel tanks, users must create user-defined vertical fuel tank
and provide parameters. (3097)

8
Aviation Environmental Design Tool
29. Dynamic grid noise metric results created in previous AEDT version fails to run in AEDT 2c SP1/SP2. A
workaround is to run the following script. (3051)
UPDATE [enter_study_name].dbo.JOB_RUN_OPTIONS
SET PERSIST_EMISSIONS_EVENT_RESULT=1, PERSIST_PERFORMANCE_EVENT_RESULT=1
WHERE JOB_ID = (enter_metric_result_ID)
30. For user-defined noise metrics, the following features are not currently supported:
• Dynamic grid
• Detailed noise report
• Time audible user-defined noise metrics
31. The C-weighted noise metric results (CDNL, CEXP, LCMAX, and TALC) are not calculated for
helicopter operations on dispersed tracks. (3054)
32. The Population Exposure Report fails to run if the Census data are stored under a directory with
spaces. This is due to a known issue with Esri – it does not accept spaces in path names. A
workaround is to store the Census data in a folder without spaces.
33. Delete all records from the TAXI_NETWORK_LINKS table after:
1) Modifying the taxi network in the study; and/or
2) Upgrading an older study to the latest version
This table gets populated when a dispersion metric result is run with Delay & Sequencing. The
existing records in this table become invalid after taxi network is updated or after study database is
upgraded. Invalid records in this table will generate the following error message in aedt.log. Empty
the TAXI_NETWORK_LINKS table and rerun the dispersion metric result.

FAA.AEE.AEDT.EmissionsDispersion.EmissionsDispersionProcess -
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at FAA.AEE.AEDT.EmissionsDispersion.ResultsExtractor.EDResultExtractor.GetTaxiEmissions
(DateTime time, EmissionsMeasureType type)
at FAA.AEE.AEDT.EmissionsDispersion.ResultsExtractor.EDResultExtractor.GetTotalTaxiEmissions
(EmissionsMeasureType type)

34. In Equipment tab, Non-Aircraft screen, only the 1990 emissions factors from the STN_GSE_EF table
are displayed for Ground Support Equipment (GSE). (4373) Emission factors for GSEs are stored in
the STN_GSE_EF and the STN_GSE_NONROAD_COEFF tables:
• When manufacture year of GSE is provided, the emissions factors in the
STN_GSE_NONROAD_COEFF table are used.
• When manufacture year of GSE is not provided, the emissions factors in the STN_GSE_EF
table are used. User-defined GSE factors are also saved to this table.
35. Uninstalling AEDT 2d may delete AEDT system and sample databases from a wrong SQL Server
instance. This could happen if AEDT 2d databases were installed on a named SQL Server instance
(e.g., (local)\sqlexpress2012) instead of a default instance (e.g., (local) or localhost). After
uninstallation, open the Microsoft SQL Server Management Studio, and manually delete the
databases if they were not removed. (4223)

9
Aviation Environmental Design Tool
Release AEDT 2c SP2
Release Date: March 13, 2017
Revision: 83.2.4163.1
Database Revisions:
• AIRPORT v2.16.1
• FLEET v3.23.0
• STUDY v1.50.0
Installer Size:
• Install AEDT 2c SP2.exe: 883 MB
• Install AEDT 2c SP2 Distributed Processing.exe: 357 MB

This AEDT 2c Service Pack 2 (SP2) release includes new features, updates, and bug fixes. A full list of
updates and bug fixes is listed below.

Instructions on how to install AEDT 2c SP2 can be found in Section 5.2 of the Installation Guide.

New and Updated Features


1. Official support of Microsoft SQL Server 2012
o Added support of Microsoft SQL Server 2012
o SQL Server 2008 R2 is still supported, but will be sunset in the next AEDT release (2d)
2. Side-by-side installation
o AEDT 2c SP2 can be installed side by side with older AEDT versions
o Distributed Processing Service is now a separate installer
3. AERMOD and AERMET version update
o Upgraded the AERMOD to version 16216r and the AERMET to version 16216
o Re-generated the sample AERMET weather files using AERMET 16216
4. Emissions dispersion computational efficiencies
o Improved speed/performance of emissions dispersion calculation execution
o Optimized the HRE file generation
o Added new Preferences settings for extracting the results in subsets
o Implemented the Progress status update functionality
5. Detailed noise report
o Integrated the detailed noise report feature into GUI
o Extended the existing Noise Report to display detailed noise results
o Added new Preferences for detailed noise result settings
6. Metric result calculation
o Implemented the Stop/Resume functionality
7. Acoustics diagnostics logging
o Added ability to generate a detailed log for every aircraft operation and receptor point
combination
8. ASIF import performance improvement
o Improved the speed of ASIF validation and import

10
Aviation Environmental Design Tool
Resolved Issues
ID Description
3795 "CIR profile does not fit on TGO track" exception is thrown for trivial difference
3685 Clicking View Receptor Set button crashes AEDT when both Noise and Emissions metric results
are selected
3648 ASIF validation does not support W (runway to runway) for track/optype element
3639 Implement Airport APT_MAIN expiration update
3606 Improve performance of loading jobs by BLL
3599 Incorrect GUI label for BADA weight parameters in Equipment tab
3580 APT_MAIN data normalization issue
3570 VALE Report displays incorrect emissions for SOx, PM2.5, and PM10
3470 ASIF import incorrectly imports dynamic grid receptor set
3460 Processing of the operations referencing runway ends with null elevation
3434 Abstract weather implementation
3420 Metric results options propagated to other metrics when multiple receptor sets are chosen
3419 No message when STUDY, FLEET, & AIRPORT databases are missing
3408 Implement try-catch to handle exceptions thrown by AEM
3406 Large MOVES HRE files cannot be processed
3384 Requirements: Contour lines
3363 Sequential running of Emission Dispersion in RunStudy command-line tool
3332 GPK logging issue
3328 Ops Edit: GSE Pop confirmation dialog behaves incorrectly
3327 Ops Edit: Prompt Gate Updates for GSE Pop Ops when layout is changed
3326 Ops Edit: Time Screen is disabled when user has switched layouts
3325 Add an operation time filter to the Results Iterator
3324 Ops Edit: Do not show "Op Time" radio button for ops that use activity profiles
3322 Ops Edit: Edit button tooltip should be "Edit" whenever button is enabled
3246 Add units to Emission Dispersion label on contour
3236 Background conc GUI controls are disabled when you copy existing job and add new wind sector
3232 Background concentrations options propagated to all metrics being created
3220 Time above (TALA) layers - wrong attribute name and layer category
3177 Ambient files for time above noise metrics are not used (i.e. Geospatially referenced ambient
option in the Set Processing Options step).
3156 Cannot create Overflight for level segment
3108 Address helo differences in dynamic grid
3101 Generate Weather Caching Scalability Requirements
3095 KC135 Departure Profile performance differences vs INM
2925 OM: Incorrect Contours (ticket #2364) - CNA Touch and Go operation profile shape
2869 Generating contour can fail due to GPK logging issue
2765 Input validation error can be hidden in Operational Profiles edit screen
2619 Changing Update Number Above Noise Level setting persists for multiple metrics being defined
2530 Transition between the arrival ground roll and the airborne arrival in the sensor path workflow
2432 System.ArgumentOutOfRangeException crash after filtering the Metric Results grid
2244 GUI Bug in Number Above Receptor Set Layer Window
2187 Modify use of RSLT_EMISSION_SEGMENT table to use null instead of 0 where appropriate
2110 update incorrect element descriptions in ASIF schema
2097 Flight performance report and emissions report for helitaxi operations do not correctly reflect
inbound vs. outbound operation type.

11
Aviation Environmental Design Tool
1409 Progress bar is not adequate for TAUD calculation

Known Issues
36. Uninstalling AEDT when another application is connected to the AEDT databases leaves any
connected databases on the server. As a workaround, delete the databases manually using
Microsoft SQL Server Management Studio. (12194)
37. After closing a study in the AEDT application, Microsoft SQL Server still maintains a connection to
the database for several minutes. To delete a study database, exit from the AEDT application first;
then delete the desired database in the Microsoft SQL Server Management Studio. (18027)
38. User settings from prior installations may not be removed exhibiting behavior such as failed contour
generation (old filename for contouring gpk). Manually delete the file C:\AEDT\DATA\[User
name]\user_settings.json where [User name] is the Windows account name under which the user is
working.
39. “Unable to upgrade study” error will be displayed during the study upgrade process if a study
contains a non-aircraft equipment group. Delete the non-aircraft equipment groups from a study
before upgrading it. (22077)
40. Aircraft equipment groups cannot be used to assign tracks to operations. User’s only access to
Operation Group Percent Distribution processing is through direct SQL injection of AIR_OPERATION
table. (1731)
41. Flight profiles are not editable when creating a user-defined aircraft in Equipment tab. Use ASIF
import in order to create a new aircraft with different flight profiles. (21323)
42. Deleting user-defined helicopter is not supported in the Equipment tab. (669)
43. Opening multiple emissions reports may show data from a different report. To avoid this issue, open
only one emissions report at a time. (21322)
44. In the Speciated Organic Gases tab in the Emissions Report, repeatedly converting units may
produce inconsistent values in the report. (21329)
45. If you get a “timeout expired” error when generating an emissions report, a workaround is to:
4) In Study tab, Database Preferences, increase the “Datacontext timeout” setting (e.g. 300
seconds).
5) Generate the “Operation Summary” emissions report first.
6) Generate the “Operation Group Summary” emission report.
46. Some airframe/engine combinations from EDMS 5.1.4.1 system data are incongruent with AEDT and
are reported “bad data integrity” errors during EDMS study import. To correct, import the aircraft as
user-defined aircraft. (21179)
47. When an EDMS study containing grid receptor sets is converted to AEDT, the rendering of receptor
locations will be slightly mismatched between EDMS and AEDT. This is because in AEDT the origin of
the grid receptor is in the south-west corner, while EDMS uses the offsets based on the center of the
grid. A workaround is to:
4) Incorporate the grid and the discrete receptors in the EDMS study into an AERMOD.INC file.
5) In AEDT, go to Study tab, Preferences, Emissions Dispersion.

12
Aviation Environmental Design Tool
6) Check the “Use AERMOD receptor grid” option and reference the .INC file from step 1 in the
“File with AERMOD receptor grid” option. This makes the application ignore the receptor set
assigned to the emissions dispersion metric result, and forces using the specified AERMOD grid
receptor. The INC file can contain both grid and discrete receptors.
48. The INM to ASIF Converter does not convert system aircraft with user modified properties (i.e.
added a custom profile, but still used the same system aircraft name). A workaround is to rename
the aircraft with a unique name so that the Converter recognizes it as a user-defined aircraft.
49. The INM to ASIF Converter does not convert user-defined helicopters and user-defined military
aircraft in an INM study. (942)
50. Airports with an expiration date set to a past date may not import via ASIF. A workaround is to
change the expiration date in the Airports database.
51. A helitaxi track imported via ASIF will be listed in the Airports Details pane, however it will not be
displayed on the map as part of the airport layout layer. To view the helitaxi track on map, view
tracks in the Metric Results tab. (21029)
52. Sensor path tracks cannot be rendered in the map display. As a workaround, in the Flight
Performance Report view the Flight Segments tab for an operation using the sensor path track.
(13236)
53. After a partial ASIF import, the application does not refresh. Restart the application to view the
imported data. (671)
54. Weather import does not take into account Airport Layout Start date. Manually confirm that the
dates for weather data being used are after the start date of the associated airport layout. (8386)
55. Processing of high fidelity weather data is not thread-safe. To compensate, set the
“NumberOfThreads” key to 1 in C:\Program
Files\FAA\AEDT\FAA.AEE.AEDT.GUI.View.Ribbon.exe.config file. (21287)
56. Flight operations specifying cruise altitude above the highest allowable specified aircraft altitude are
processed. Manually confirm cruise altitude on the operation against the BADA cruise altitude limit.
(6676)
57. If the BADA energy share factor is not present in the FLT_ANP_BADA_ENERGYSHARE table for the
aircraft's ANP ID/BADA ID combination, it can cause an infinite loop when processing such aircraft.
The BADA energy share factor is used in modeling the transition from the ANP flight regime for the
terminal area and the BADA flight regime for the cruise portion of the flight. A workaround is to
manually insert a record into this table. (2099)
58. AEDT is unable to process 3CD terrain files. A workaround is to use GridFloat files instead. (929)
59. Generating noise contour for imported metric result is not supported. To examine results, view the
receptor set. (21335)
60. The noise grid file exported from AEDT is incorrectly scaled. (21963)
61. An AEDT generated shapefile cannot be imported into Google Earth Pro. (21979)
62. Noise contours may be displaced on the map (i.e. does not align with the receptor set) if the X and Y
spacings are not the same. (22072)
63. When applying Delay & Sequencing, air operations based on operational profiles with “Operation
Count” values that are small, e.g. less than one operation per scenario duration, are subject to a
quantization error in the assignment of the operation time.
13
Aviation Environmental Design Tool
64. Emissions dispersion metric results created in previous AEDT version (e.g., AEDT 2c or AEDT 2b)
cannot be run in AEDT 2c SP1. A workaround is to copy the existing dispersion metric result and
create a new one. (3237)
65. Dispersed tracks are not supported for emissions dispersion modeling.
66. On a low resolution computer screen, the bottom portion of the Edit Operations wizard cannot be
accessed. (3113)
67. In order to generate results for vertical fuel tanks, users must create user-defined vertical fuel tank
and provide parameters. (3097)
68. Dynamic grid noise metric results created in previous AEDT version fails to run in AEDT 2c SP1/SP2. A
workaround is to run the following script:
UPDATE [enter_study_name].dbo.JOB_RUN_OPTIONS
SET PERSIST_EMISSIONS_EVENT_RESULT=1, PERSIST_PERFORMANCE_EVENT_RESULT=1
WHERE JOB_ID = (enter_metric_result_ID)
The pre-defined metric result #3 in STUDY_WXYZ fails the dynamic grid processing for the same
reason. (3051)
69. In the Fleet database, helicopter directivity data for B206B3, B407, B427, B429, and B430 are either
missing or incorrect. (2900)
70. The 2c SP2 installer does not support upgrading the previous AEDT version (2c SP1). (3783)
71. There is a mismatch between the metric result progress bar and the progress bar at the bottom of
the screen. The State progress bar for a metric result may display 100% while it is still being run.
(3789)
72. Acoustics diagnostics logging is only supported for point-type receptors and for fixed-wing aircraft. It
generates log files in two different locations – C:\AEDT and C:\AEDT\Logs
73. In order for the stop & resume of HRE file generation to work, both “Extract emissions results in
subsets” and “Save interim results during HRE generation” settings in the Emissions Dispersion
Preferences screen must be checked.

14
Aviation Environmental Design Tool
Release AEDT 2c SP1
Release Date: December 19, 2016
Installer Size: 628 MB
Revision: 79.1.3328.1
Database Revisions:
• AIRPORT v2.16.1
• FLEET v3.22.1
• STUDY v1.48.1

This AEDT 2c Service Pack 1 (SP1) release includes new features, updates, and bug fixes. A full list of
updates and bug fixes is listed below.

Instructions on how to install AEDT 2c SP1 can be found in Section 5.2 of the Installation Guide. Remove
previous AEDT version before installing AEDT 2c SP1. A warning message will be displayed if you attempt
to install AEDT 2c SP1 on a computer with AEDT already installed.

New and Updated Features


1. Dynamic grid support for all dB-based noise metrics
o Implemented reports for dynamic grid, noise metric results
 Flight performance report
 Emissions report
 Noise report
 Population exposure report
o Added terrain support
o Added ability to save the dynamic grid contour expansion level per metric result
o Added support of dynamic grid for user-defined airport
2. Edit operations process
o Added ability to edit single operation
o Added ability to edit bulk operations at once
3. Emissions dispersion output selection
o Implemented ability to select specific Source Groups, Averages, and Rankings in Define
Metric Results wizard, effectively limiting the AERMOD runs
 Support computation of daily maximum values for the 1-hour averages (NOx and
SOx)
o Implemented ability to select specific Source Groups, Averages, and Rankings for viewing
results
 Pollutant concentration layer
 Concentration contour layer
 Emissions dispersion report
o Added ability to create contour for emissions dispersion metric result using a grid receptor
set
o Added ability to create a receptor using distance in Meters
4. Layer improvements
o Changed noise contour values in the legend to a single value instead of a range
o Extended "Area & Percent Area" feature in receptor set layer to other noise metrics
o Fixed issues with updating color properties
5. Background concentrations improvements
o Added ability to set user-defined wind categories

15
Aviation Environmental Design Tool
o Added ability to save wind categories per metric result
6. MOVES AERMOD Files import improvements
o Added ability to create a “MOVES scenario” by importing MOVES AERMOD files and store
more than one MOVES scenario in a study
o Added ability to select the MOVES scenario in Define Metric Results wizard
7. Feature activation in Study Preferences
o Added centralized control for activating different features (e.g. Time Audible Metrics)
8. Additional system logging
o Added logging of system versions and memory information to aedt.log

Resolved Issues
ID Description
3029 Detailed Noise results are incorrectly computed for MetricAll and Percent for all exposure
metrics
3015 Non-Aircraft Single Day Duration - Not Updated in Annualization UI
3014 Missing data in .PFL file - Emission Dispersion fails
3013 Extra and Missing data in .SFC file - Emission Dispersion fails
3012 Missing data in .MET - Emission Dispersion fails
3002 Edit Terminal / Gate Dialogs - Add a Units Selector
2967 Generate Study Report does not update after study modification
2961 Emission Dispersion run fail for non-aircraft operation with background concentration
2956 Upgrading a study fails if AEDT is installed on non-default location
2954 BG File Start time needs to match Non-Aircraft Start Time
2953 In Equipment tab, APU field is not updated after copying a fixed-wing aircraft
2923 Identify mismatches between duration of operations and MET data and inform user
2919 Failure to load a single corrupt study stops loading of all studies, fix logic to load rest and log
failure
2917 Extend "Area & Percent Area" feature in receptor set layer (TAUD implementation) to other
noise metrics
2916 Persist user's selection of units for receptors
2898 add the release height field to the Edit Heligate dialog
2876 assign airport elevation as default when a new receptor is created
2874 Correct distances from the arrival and departure airports
2873 Review HiFi Weather Report and Update Backlog
2870 insert non-null release height, sigmaY0, and sigmaZ0 for a new gate/terminal created by airport
layout design
2834 Improve the integration of MOVES files for emissions dispersion
2822 Hide irrelevant options and reorganize the Set Processing Options screen
2814 Support PEM report for dynamic grid jobs
2805 Support dynamic grid processing for user-defined airport
2775 Moving a track point using Drag tool in Airport Layout Design resets track data
2768 Create Runup & HeliTaxi Wizards do not accept operation count less than one
2766 Hourly BC file persisted when copying metric result
2739 AEDT crashes when Hourly BC file is already open
2738 Users experiencing AEDT crashes after Windows update
2736 Running detailed noise metric result fails (noise storage option = event)
2731 Airport with certain facility types cannot be added or seen by user
2671 Improve contour generation GPK
2650 Cannot copy & paste value into numeric text box
16
Aviation Environmental Design Tool
2641 No defaults for Time Above Noise Metrics options
2634 AERMOD BACKGROUND error when running air op ID 2118 in STUDY_DULLES
2626 Invalid wind speed categories can be saved
2624 Implement emissions calculation for the dynamic grid noise metric results
2569 Support creating helicopter overflight operation in Create Aircraft Op wizard
2567 Symbology for contours to display single level instead of range
2556 OM: typo in the contour error message
2544 Add error handling to AsifStudyValidator.validateAsifTrkOpSetTrackRefAirport()
2539 Error importing to remote SQL Server instance
2521 Support for Additional System Logging
2435 Background concentrations options are not recreated in the UI when an emissions dispersion
metric is copied
2433 When a new non-emissions dispersion metric is created a default wind sector is also created
2407 OPM: when track id and sensor path id are both null, no events are created but no error
messages
2339 Background concentration units are not converted properly for NOx, SOx, and PMx
2324 Update Metric Result Input Report and Study Input Report
2292 Add display of background concentrations options in the metric results summary view
2282 Metric Results Details tab displays incorrect storage values for PM10 and PM25
2268 UX: Implement Wind Speed Categories pane as an additional option for Definitions in the
Weather tab
2255 INM2ASIF: Converter Support for Grid Receptors with Offsets
2254 EDMS2ASIF: Converter Support for Grid Receptors with Offsets
2253 ASIF: Import Support for Grid Receptors with Offsets
2252 STUDY: Stored Procedure Update for Importing Grid Receptors with Offsets
2248 Provide summary of background concentration settings in Metric Results summary
2239 Bug fixes for the specification of background concentrations
2232 AFCM configurations of the B787 are not imported correctly
2230 Clean-up the ConnectionStrings.config
2214 New renderer applied before pressing OK
2205 Investigate MERRA-2 as a solution to coordinate transform problem
2192 Annualization incorrectly imported from an INM study with reference cases
2178 If DB connection is misconfigured a misleading error message is displayed
2167 Address Layer issues
2164 EDM if you select "Generate CON files" in preference for PM10 and PM25, aermod will fail
2163 EDM non-NAAQS option does not work correctly for annual jobs
2162 Background concentrations options: Sectors are not in order
2159 ReceptorSet new renderer not saved
2157 Color Layer Properties for Contour thickness doesn’t work
2156 Receptor Set NANL disappears when assigning new renderer
2155 UX fixes for Number Above Threshold in Define Metric Results, Set Processing Options
2148 Implement a more robust solution for entering numbers in text fields
2144 Don't show Receptor Set dialog for NANL metric when Metric Result hasn't run
2140 Importing an ASIF/EDMS file does not report all airport name conflicts
2139 Self-registration error for DelayModelCOM.exe when uninstalling
2136 Errant quotes in message title and body in background concentrations options
2135 Background concentrations options: Annual value is cleared after switching to "Use File" and
back again
2131 Updated receptor set color scheme not reflected in layer list symbology
17
Aviation Environmental Design Tool
2117 Background concentrations options: Start value is restricted to range 0 to 3
2109 Using LAMAX for Detailed Noise Grid Fails
2106 EDM: annual PLT should have PLT groups in addition to ALL
2102 EDM: annual plt file shows non-existing measured date in attribute
2101 EDM: cannot produce annual plt file
2095 Upgrading a study crashes if the STUDY database does not exist on the SQL Server instance
2092 Remove records from FLT_ENGINE_MODS and FLT_APU tables when deleting fixed-wing aircraft
2079 Extend aedt.log with .NET version information
2066 Mixed turbofan engines not treated correctly in AEM/DAM
2023 Finish implementation of signing all exes and dlls
1978 AEDT installation has Feature transfer error and Access denied warnings
1940 "Dynamic grid contour expansion level" in Define Metric Results wizard is not used
1865 Taxi-gate intersection location calculation is incorrect
1864 Taxi network runways use default runway width
1854 TAUD contour color mismatch
1853 DNL Contour plot color mismatch
1814 Study Import Wizard: review and fix UI issues
1724 Fix Open or Study Import code to use MVVM when referencing credentials
1681 EOL related issues for VALE report
1459 Layer legend within AEDT is not refreshed if Layer definition has been updated
1430 AEDT crashes on startup if system databases are not installed on local SQL Server instance
1379 Contour Layer Properties - Line Thickness
1368 Changing the color properties of time audible layers does not work
1334 Import: User defined airport zone information is not persisted to database
1292 OM: Dynamic grid process assumes that annualization ID = scenario ID
1234 Enable User Defined Airport in INM to ASIF converter does not work
1203 Setting line thickness for single range within contour sets thickness for all ranges
980 FLEET ANP weight categories are incorrect for 5 aircraft
979 Export of Some Aircraft Only Includes STANDARD Profiles due to empty spaces in the PROF_ID1
column
977 Replace "HD500D" with "H500D" in [FLT_ANP_HELICOPTER_DIRECTIVITY].[DIRECT_ID] field
976 ASIF import of INM study (with case reference) creates incorrect annualization mapping
955 Remote Taskmaster does not support "ALL" terrain file type
692 Implement Thrust types other than pounds for runup operations

Known Issues
1. Uninstalling AEDT when another application is connected to the AEDT databases leaves any
connected databases on the server. As a workaround, delete the databases manually using
Microsoft SQL Server Management Studio. (12194)
2. After closing a study in the AEDT application, Microsoft SQL Server still maintains a connection to
the database for several minutes. To delete a study database, exit from the AEDT application first;
then delete the desired database in the Microsoft SQL Server Management Studio. (18027)
3. User settings from prior installations may not be removed exhibiting behavior such as failed contour
generation (old filename for contouring gpk). Manually delete the file C:\AEDT\DATA\[User
name]\user_settings.json where [User name] is the Windows account name under which the user is
working.

18
Aviation Environmental Design Tool
4. “Unable to upgrade study” error will be displayed during the study upgrade process if a study
contains a non-aircraft equipment group. Delete the non-aircraft equipment groups from a study
before upgrading it. (22077)
5. Aircraft equipment groups cannot be used to assign tracks to operations. User’s only access to
Operation Group Percent Distribution processing is through direct SQL injection of AIR_OPERATION
table. (1731)
6. Flight profiles are not editable when creating a user-defined aircraft in Equipment tab. Use ASIF
import in order to create a new aircraft with different flight profiles. (21323)
7. Deleting user-defined helicopter is not supported in the Equipment tab. (669)
8. Flight performance report and emissions report for helitaxi operations do not correctly reflect
inbound vs. outbound operation type. (2097)
9. Opening multiple emissions reports may show data from a different report. To avoid this issue, open
only one emissions report at a time. (21322)
10. In the Speciated Organic Gases tab in the Emissions Report, repeatedly converting units may
produce inconsistent values in the report. (21329)
11. If you get a “timeout expired” error when generating an emissions report, a workaround is to:
1) In Study tab, Database Preferences, increase the “Datacontext timeout” setting (e.g. 300
seconds).
2) Generate the “Operation Summary” emissions report first.
3) Generate the “Operation Group Summary” emission report.
12. Some airframe/engine combinations from EDMS 5.1.4.1 system data are incongruent with AEDT and
are reported “bad data integrity” errors during EDMS study import. To correct, import the aircraft as
user-defined aircraft. (21179)
13. When an EDMS study containing grid receptor sets is converted to AEDT, the rendering of receptor
locations will be slightly mismatched between EDMS and AEDT. This is because in AEDT the origin of
the grid receptor is in the south-west corner, while EDMS uses the offsets based on the center of the
grid. A workaround is to:
1) Incorporate the grid and the discrete receptors in the EDMS study into an AERMOD.INC file.
2) In AEDT, go to Study tab, Preferences, Emissions Dispersion.
3) Check the “Use AERMOD receptor grid” option and reference the .INC file from step 1 in the
“File with AERMOD receptor grid” option. This makes the application ignore the receptor set
assigned to the emissions dispersion metric result, and forces using the specified AERMOD grid
receptor. The INC file can contain both grid and discrete receptors.
14. The INM to ASIF Converter does not convert system aircraft with user modified properties (i.e.
added a custom profile, but still used the same system aircraft name). A workaround is to rename
the aircraft with a unique name so that the Converter recognizes it as a user-defined aircraft.
15. The INM to ASIF Converter does not convert user-defined helicopters and user-defined military
aircraft in an INM study. (942)
16. Airports with an expiration date set to a past date may not import via ASIF. A workaround is to
change the expiration date in the Airports database.

19
Aviation Environmental Design Tool
17. A helitaxi track imported via ASIF will be listed in the Airports Details pane, however it will not be
displayed on the map as part of the airport layout layer. To view the helitaxi track on map, view
tracks in the Metric Results tab. (21029)
18. Sensor path tracks cannot be rendered in the map display. As a workaround, in the Flight
Performance Report view the Flight Segments tab for an operation using the sensor path track.
(13236)
19. After a partial ASIF import, the application does not refresh. Restart the application to view the
imported data. (671)
20. Weather import does not take into account Airport Layout Start date. Manually confirm that the
dates for weather data being used are after the start date of the associated airport layout. (8386)
21. Processing of high fidelity weather data is not thread-safe. To compensate, set the
“NumberOfThreads” key to 1 in C:\Program
Files\FAA\AEDT\FAA.AEE.AEDT.GUI.View.Ribbon.exe.config file. (21287)
22. Flight operations specifying cruise altitude above the highest allowable specified aircraft altitude are
processed. Manually confirm cruise altitude on the operation against the BADA cruise altitude limit.
(6676)
23. If the BADA energy share factor is not present in the FLT_ANP_BADA_ENERGYSHARE table for the
aircraft's ANP ID/BADA ID combination, it can cause an infinite loop when processing such aircraft.
The BADA energy share factor is used in modeling the transition from the ANP flight regime for the
terminal area and the BADA flight regime for the cruise portion of the flight. A workaround is to
manually insert a record into this table. (2099)
24. AEDT is unable to process 3CD terrain files. A workaround is to use GridFloat files instead. (929)
25. Generating noise contour for imported metric result is not supported. To examine results, view the
receptor set. (21335)
26. The noise grid file exported from AEDT is incorrectly scaled. (21963)
27. An AEDT generated shapefile cannot be imported into Google Earth Pro. (21979)
28. Noise contours may be displaced on the map (i.e. does not align with the receptor set) if the X and Y
spacings are not the same. (22072)
29. When applying Delay & Sequencing, air operations based on operational profiles with “Operation
Count” values that are small, e.g. less than one operation per scenario duration, are subject to a
quantization error in the assignment of the operation time.
30. Emissions dispersion metric results created in previous AEDT version (e.g., AEDT 2c or AEDT 2b)
cannot be run in AEDT 2c SP1. A workaround is to copy the existing dispersion metric result and
create a new one. (3237)
31. Dispersed tracks are not supported for emissions dispersion modeling.
32. Ambient files for time above noise metrics are not used (i.e. Geospatially referenced ambient option
in the Set Processing Options step). (3177)
33. On a low resolution computer screen, the bottom portion of the Edit Operations wizard cannot be
accessed. (3113)
34. In order to generate results for vertical fuel tanks, users must create user-defined vertical fuel tank
and provide parameters. (3097)
20
Aviation Environmental Design Tool
35. Dynamic grid noise metric results created in previous AEDT version fails to run in AEDT 2c SP1. A
workaround is to run the following script:
UPDATE [enter_study_name].dbo.JOB_RUN_OPTIONS
SET PERSIST_EMISSIONS_EVENT_RESULT=1, PERSIST_PERFORMANCE_EVENT_RESULT=1
WHERE JOB_ID = (enter_metric_result_ID)
The pre-defined metric result #3 in STUDY_WXYZ fails the dynamic grid processing for the same
reason. (3051)
36. In the Fleet database, helicopter directivity data for B206B3, B407, B427, B429, and B430 are either
missing or incorrect. (2900)
37. “System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values”
crash may occur after filtering the Metric Results grid. (2432)

21
Aviation Environmental Design Tool
Release AEDT 2c
Release Date: September 12, 2016
Installer Size: 622 MB
Revision: 75.0.2001.1
Database Revisions:
• AIRPORT v2.16.0
• FLEET v3.21.0
• STUDY v1.46.0

This AEDT 2c release includes new features, updates, and bug fixes. A full list of updates and bug fixes is
listed below.

Instructions on how to install AEDT 2c can be found in Section 5.2 of the Installation Guide.

Installing AEDT 2b and AEDT 2c applications on the same computer is not supported. A warning message
will be displayed if you attempt to install AEDT 2c on a computer with AEDT 2b already installed.
Remove AEDT 2b before installing AEDT 2c.

New Features
1. Number above noise level: For LAMAX, LCMAX, SEL, and CEXP noise metrics, AEDT supports
calculating the number of operations that exceed the specified decibel threshold.
2. Background emissions concentrations: AEDT supports AERMOD's modeling of background
concentrations for CO, NOx, SOx, PM10, and PM2.5. It estimates cumulative ambient concentration
impacts (background and airport sources).
3. Environmental justice capabilities: The analyst can explore select US Census Bureau, American
Community Survey (ACS) data in support of the identification of potential environmental justice
populations.
4. Improvements to the contouring algorithm for complex contour configurations including islands.
5. Improvements to the rendering of imported GIS layers.
6. Receptor grid offset: The Update Grid Origin button in Receptor Details dialog changes the latitude
and longitude of the receptor to the airport origin by using offsets.
7. Delete annualization button: Deleting annualization is supported.
8. Install prerequisite .NET Framework 4.6.1 during installation.
9. Extended the GlobalMapper license.

Resolved Issues
Item ID Description
959 OM: INM2ASIF Converter does not convert airport and receptor elevation in meters into feet
1179 A user can accidentally delete a report in the Open Reports list
1207 Disable the Run button for finished metric results
1291 Installing Sprint 69 installer over Sprint 68 leaves ArcGISRuntime10.2.2 folder behind
1330 OM: Want ability to export airport layout layer (runways) as shapefile
1335 Runup and terrain bug - OM ticket 2111
1340 AEDT crash when Generating Impact Sets for non-DNL metrics
1356 Application crashes with crossthreading exception when contour generation fails.
1364 Update the copyright information in the AEDT 2b installer
1371 No indication that Operational Profile has input validation errors in Definitions tab
1372 Exception & crash when loading a layered boundary file for restrict by boundary

22
Aviation Environmental Design Tool
1373 Receptor can be saved with input validation errors in Definitions tab
1374 No indication that Operational Profile has input validation errors in Definitions tab
1375 In Definitions tab, Airport Weather Details appear to be saved with invalid data
1376 Weather details aren't saved in "Generate emissions dispersion weather files" screen
1388 Terrain cannot be changed from job to job
1389 Ambient cannot be changed from job to job
1390 In Set Processing Options screen, ambient threshold text boxes are not displayed for user-
defined Time Above metric
1396 LOS with a boundary takes long time to run
1401 Receptor Details screen needs re-work
1403 Deleting Receptors is very slow.
1429 index out of range exception when generating a contour with single step
1431 Bundle Microsoft C++ Redistributable Packages in AEDT installer
1442 User-controllable sensor path preprocessing switch default to off
1461 GUI profile based new airoperation does not follow the quaterhourly schedule
1462 Remove FAA.AEE.AEDT.EDM.GCM.GridCellManager.exe from installer
1533 Measured Date in concentration layer attributes is 1/1/0001
1586 Implement new GlobalMapper license in AEDT 2b code base
1591 Definitions AirportWeather combobox is empty after creating a new airport.
1606 Update installer to include new RunStudy app
1612 Receptor edit dialog treat null as 0
1613 exception & crash when viewing attributes for THC concentration layer
1626 Apply UX guidelines to the Import Study - Data Conflicts screen
1654 Aggregated VALE report issue
1680 Concentration Layer Attributes displaying the wrong column label for PM10 and PM25.
1682 VALE metric results creation - issue related to user input for analysis year
1721 Investigate DGNoiseValues.csv being smaller than Receptor Set Receptor Count
1722 Study Import Wizard, Review Study Content step: Number of errors is always zero
1723 Study Import Wizard, Review Study Content step: Next button is not enabled until user clicks on
page
1726 Study Import Wizard, Choose Study Location step: context management issues
1729 Update description in Study tab, Preferences screen
1755 Measured Date in concentration layer is converted to local time
1758 UX bug: application crashes when opening study created on different install location
1759 UX bug: if a study name contains apostrophe, the Open Study dialog displays - can't connect to
database server error
1760 Refresh cache when terrain and ambient files are changed in GUI
1769 ASIF import does not populate the taxi in/out time in AIR_OPERATION table
1787 Fix copyright for all AEDT executables and assemblies
1788 In the Import Study dialog, check for duplicate study name before starting the import
1802 Add new RunStudy to installer
1817 LAEQN receptor set layer attributes always display 0 dB values
1872 GUI layout issue in Import Partial ASIF dialog
1900 Add BatchAnalysis.dll to installer
1924 Incorrect "Cannot delete taxipath - used for delay sequencing" error
1936 Pop exposure fails due to problems with contour islands
1947 Incorrect values/label for flight profiles in Equipment tab
1956 Add date and time values to the emissions-dispersion output reports
1957 Install prerequisite .NET Framework 4.6.1 during installation
23
Aviation Environmental Design Tool
1958 Change “Altitude AFE (ft)” label in Edit Track dialog to MSL
1987 Change units in the Flight Segment report
2000 Remove Altitude, Message Time, and Altitude Control columns from Edit Helitaxi dialog
2012 ESRI cannot convert Taxipaths, TaxiWays, Tracks into shapefiles
2017 Hide the "height above terrain" field from GUI for a grid type receptor
2101 EDM: cannot produce annual plt file
2102 EDM: annual plt file shows non-existing measured date in attribute

Known Issues
1. Some airframe/engine combinations from EDMS 5.1.4.1 system data are incongruent with AEDT and
are reported “bad data integrity” errors during EDMS study import. To correct, import the aircraft as
user-defined aircraft. (21179)
2. When an EDMS study containing grid receptor sets is converted to AEDT, the rendering of receptor
locations will be slightly mismatched between EDMS and AEDT. This is because in AEDT the origin of
the grid receptor is in the bottom left corner, while EDMS uses the offsets based on the center of
the grid. A workaround is to:
1) Incorporate the grid and the discrete receptors in the EDMS study into an AERMOD.INC file.
2) In AEDT, go to Study tab, Preferences, Emissions Dispersion.
3) Check the “Use AERMOD receptor grid” option and reference the .INC file from step 1 in the
“File with AERMOD receptor grid” option. This makes the application ignore the receptor set
assigned to the emissions dispersion metric result, and forces using the specified AERMOD grid
receptor. The INC file can contain both grid and discrete receptors.
3. Flight profiles are not editable when creating a user-defined aircraft in Equipment tab. Use ASIF
import in order to create a new aircraft with different flight profiles. (21323)
4. Deleting user-defined helicopter is not supported in the Equipment tab. (669)
5. Flight performance report and emissions report for helitaxi operations do not correctly reflect
inbound vs. outbound operation type. (2097)
6. Opening multiple emissions reports may show data from a different report. To avoid this issue, open
only one emissions report at a time. (21322)
7. In the INM to ASIF Converter tool, the “Enable User Defined Airport” option is not supported. (1234)
8. In the Speciated Organic Gases tab in the Emissions Report, repeatedly converting units may
produce inconsistent values in the report. (21329)
9. Generating noise contour for imported metric result is not supported. To examine results, view the
receptor set. (21335)
10. A helitaxi track imported via ASIF will be listed in the Airports Details pane, however it will not be
displayed on the map as part of the airport layout layer. To view the helitaxi track on map, view
tracks in the Metric Results tab. (21029)
11. After a partial ASIF import, the application does not refresh. Restart the application to view the
imported data. (671)
12. If you get a “timeout expired” error when generating an emissions report, a workaround is to:
1) In Study tab, Database Preferences, increase the “Datacontext timeout” setting (e.g. 300
seconds).
2) Generate the “Operation Summary” emissions report first.
3) Generate the “Operation Group Summary” emission report.
13. User settings from prior installations may not be removed exhibiting behavior such as failed contour
generation (old filename for contouring gpk). Manually delete the file C:\AEDT\DATA\[User
name]\user_settings.json where [User name] is the Windows account name under which the user is
working.

24
Aviation Environmental Design Tool
14. Uninstalling AEDT when another application is connected to the AEDT databases leaves any
connected databases on the server. As a workaround, delete the databases manually using
Microsoft SQL Server Management Studio. (12194)
15. After closing a study in the AEDT application, Microsoft SQL Server still maintains a connection to
the database for several minutes. To delete a study database, exit from the AEDT application first;
then delete the desired database in the Microsoft SQL Server Management Studio. (18027)
16. Aircraft equipment groups cannot be used to assign tracks to operations. User’s only access to
Operation Group Percent Distribution processing is through direct SQL injection of AIR_OPERATION
table. (1731)
17. Airports with an expiration date set to a past date may not import via ASIF. A workaround is to
change the expiration date in the Airports database.
18. The INM to ASIF Converter will not convert system aircraft with user modified properties (i.e. added
a custom profile, but still used the same system aircraft name). A workaround is to rename the
aircraft with a unique name so that the Converter recognizes it as a user-defined aircraft.
19. Weather import does not take into account Airport Layout Start date. Manually confirm that the
dates for weather data being used are after the start date of the associated airport layout. (8386)
20. Sensor path tracks cannot be rendered in the map display. As a workaround, in the Flight
Performance Report view the Flight Segments tab for an operation using the sensor path track.
(13236)
21. Flight operations specifying cruise altitude above the highest allowable specified aircraft altitude are
processed. Manually confirm cruise altitude on the operation against the BADA cruise altitude limit.
(6676)
22. Processing of high fidelity weather data is not thread-safe. To compensate, set the
“NumberOfThreads” key to 1 in C:\Program
Files\FAA\AEDT\FAA.AEE.AEDT.GUI.View.Ribbon.exe.config file. (21287)
23. If the BADA energy share factor is not present in the FLT_ANP_BADA_ENERGYSHARE table for the
aircraft's ANP ID/BADA ID combination, it can cause an infinite loop when processing such aircraft.
The BADA energy share factor is used in modeling the transition from the ANP flight regime for the
terminal area and the BADA flight regime for the cruise portion of the flight. A workaround is to
manually insert a record into this table. (2099)
24. Noise metric results using dynamic grid receptor sets will not be processed when airport codes are
user-defined. As a workaround, temporarily reassign the user-define airport code to an ICAO code.
(21339)
25. “Unable to upgrade study” error will be displayed during the study upgrade process if a study
contains a non-aircraft equipment group. Delete the non-aircraft equipment groups from a study
before upgrading it. (22077)
26. AEDT is unable to process 3CD terrain files. A workaround is to use GridFloat files instead. (929)
27. The noise grid file exported from AEDT is incorrectly scaled. (21963)
28. An AEDT generated shapefile cannot be imported into Google Earth Pro. (21979)
29. Taxi-gate intersection location calculation is incorrect. (1865)
30. Taxi network runways use the default runway width (20 meters) instead of the defined runway
width. (1864)
31. When exporting some aircraft from the Equipment tab, only the STANDARD profiles are included,
not ICAO-A and ICAO-B. (979)
32. Noise contours may be displaced on the map (i.e. does not align with the receptor set) if the X and Y
spacings are not the same. (22072)
33. When applying Delay & Sequencing, air operations based on operational profiles with “Operation
Count” values that are small, e.g. less than one operation per scenario duration, are subject to a
quantization error in the assignment of the operation time.
25
Aviation Environmental Design Tool
34. In Create Runup Operation wizard, the units for the Thrust field does not change for military aircraft.
(692)
35. User-defined helicopters and user-defined military aircraft in an INM study are not converted by the
INM to ASIF Converter Tool. (942)
36. "Dynamic grid contour expansion level" in Define Metric Results wizard is not used. (1940)
37. OM: Dynamic grid process assumes that annualization ID = scenario ID. (1292)
38. OM: Remote Taskmaster does not support "ALL" terrain file type. Running distributed processing
with terrain is not supported. (955)
39. ASIF import of INM study with case reference (multiple scenarios pointing to the same case) creates
incorrect annualization mapping. (976)
40. Background concentrations known issues:
• Changing intermediate wind sector definitions after they have all been defined can lead to
overlapping sectors which will generate AERMOD errors. It is recommended that the user
sequentially define contiguous sectors starting with the last or bottom-most sector and not
attempt to change intermediate sector start angles after they have all been defined. Note that
the minimum sector area is 30 degrees
• All sector angles must be between 0 and 359. Negative values are not allowed.
• If the spinners on the Start angle specification are not responding and if the field is not
accepting text input, the minimum angle between the sector and the following sector is too
small. Adjust the angle of the adjacent sector first to enable input.
• On occasion the Next button on the wizard will be disabled even after specifying a non-hourly
annual background concentration value. If that happens click somewhere else in the GUI
window to refresh focus and enable the Next button.
• Note that AERMOD has a requirement that modeling of PM2.5 emissions requires a year’s worth
of input emissions and weather data (this is for any emissions-dispersion run – irrespective of
background concentrations).
• The non-hourly WSPEED background concentrations uses the default wind speed categories of
1.54, 3.09, 5.14, 8.23, 10.8 (m/s). The ability to change these values will be provided in AEDT 2c
SP1.
• For all pollutants (except for CO), the user should provide the input in micrograms per meter3.
All other units will not be correctly converted to the output units. Note, conversion from ppm
for CO will work.

Release AEDT 2b SP3


Release Date: June 13, 2016
Installer Size: 586 MB
Revision: 70.3.790.1
Database Revisions:
• AIRPORT v2.16.0
• FLEET v3.20.2
• STUDY v1.45.0

This AEDT 2b Service Pack 3 (SP3) includes several bug fixes and updates. A full list of bug fixes and
updates is listed below.

Instructions on how to install AEDT 2b SP3 or update to SP3 from an existing release of AEDT 2b can be
found in Section 5.2 of the Installation Guide.

26
Aviation Environmental Design Tool
New Features
1. Time Audible:
• Multiple metrics
• Support for non-24 hours
• Support for boundary files
2. VALE Report workflow improvements:
• Multiple analysis year VALE reporting
• Support for equipment lifetime processing
3. Addition of fuel consumption and emissions for military aircraft (and aircraft with thrust type =
“other”)
4. Improvements to the import of EDMS studies - import with inconsistent or missing airport data
5. Improvements to the study upgrade process - supports upgrading studies from revision 1.43.1 up to
the current revision
6. Consolidation of ASIF, EDMS, and INM import into the Import Study wizard
7. Implemented FOA 3.0 as the default and the only PM model.
• Removed the PM Model choice in the Study > Preferences > Emissions screen and in the Create
Annualization wizard.
8. Default GSEs are pre-selected in the Create Aircraft Operation wizard, Choose GSE/APU step.
Default APU is displayed.

Warnings
1. When installing AEDT, if you wish to save any user modifications to AEDT system databases
(STUDY_XXXX, AIRPORT, or FLEET), perform a manual backup of the databases before uninstalling
the prior release of AEDT.
2. Existing user-created studies need to be upgraded to the current release in order to use them in
AEDT 2b SP2.
3. AEDT supports upgrading studies that are one release prior to the current release via Study tab >
Open > Show All Versions checkbox.
a) It is strongly recommended to select the “Backup study and upgrade” option to preserve a copy
of the existing study database before upgrading.
b) If the upgrade process fails, the study database could be corrupted and can only be restored
from a backup file.
c) After upgrading a user-defined study, reset and re-run the existing metric results in the study.
4. Conversion of AEDT 2a studies to AEDT 2b is supported through the stand-alone AEDT 2a to 2b
converter.
5. If you get the following errors when starting AEDT after installing AEDT 2b SP2, follow the steps
below.
• Exception 1: System.ComponentModel.Win32Exception (0x80004005): The system cannot find
the file specified
• Exception 2: System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-
specific error occurred while establishing a connection to SQL Server. The server was not found
or was not accessible. Verify that the instance name is correct and that SQL Server is configured
to allow remote connections.

Workaround steps:
a) Uninstall AEDT and make sure that the C:\AEDT folder is deleted.
b) Restart the computer.
c) Install the AEDT 2b SP2 again.
27
Aviation Environmental Design Tool
Resolved Issues
Item ID Description
688 In Set Processing Options screen, default atmospheric absorption model should be SAE-ARP-
5534
761 Unsupported en-route ANP flight between controls should not cause flight failure
951 APM Sensor Path: Speed profile data integrity issue in PDARS operations
957 Approach bank adjustment is applied to all operating conditions
996 Allow setting to determine location of C:\AEDT folder
1126 Table [GSE_USER_EF ] has a blank space at the end of the table name
1141 Provide enumeration values used in Study DB
1155 Upper air file (FSL) weather parser bug
1199 Formatting of values in Noise Reports for different metrics
1223 Setting invalid CSV for MOVES Emissions Inventory Results crashes
1295 Study input report rounds up the Fuel Sulfur Content and Sulfur Conversion Rate
1289 Track segment ordering bug - AEDT uses SEGMENT_ID instead of SEGMENT_NUM
1300 Disable the View Contour button for non-grid receptor set
1302 Wrong label for Time Averaging Constant in Metric Details and disabling constant isn't saved.
1304 Incorrect context management in Create Annualization wizard, Set Processing Options screen
1325 Incorrect context management for Study tab, Emissions Preferences text fields
1326 Update the default FOA3 settings in the INM2ASIF Converter to default to FOA3.0
1082 Upgrade ArcGIS Runtime for WPF to 10.2.5
1117 Add a vertical scroll bar to Choose Gate step in Create Aircraft Op wizard
1118 OM: Exported concentration layer shapefile has empty values for pollutant concentrations
1119 OM: Remove "Shape_Leng" column from the exported tracks layer shapefile
1120 The "Num Ops" column in Emissions report (Operations Detail) shows 0 if value is less than 0.1.
1121 Receptor set noise values are all zero for user-defined noise metrics
1127 Arrival Emissions not being generated in Emissions Report
1154 Cannot save layer names with hyphens to shapefile
1169 Concentration Index for Emissions attributes garbled text when re-importing from shapefile.
1176 Confusing error popup when database is not accessible
1193 Add Arr/Dep Gate columns to Operations tab, Aircraft view
1194 Too tall row height issue in the Non-aircraft grid in Operations tab
1238 Distributed Processing dialog issue - column names and labels are cut off
1249 Add population count column to layer attributes for population receptors.
893 UX bug: user is unable to enter and edit emissions factors for user-defined GSE in Equipment tab
894 UX bug: Adding/deleting points in Edit Taxiway dialog does not work
899 Update the detailed noise SQL script - add how to update max character limit for XML data
906 Add additional sample partial ASIF files to the installer
973 Incorrect error message for a touch & go track in Edit Track dialog
981 User-defined GSEs do not produce emissions results
1062 Change the Run Start Time and Run End Time in Metric Results Detailed workspace to regular
textbox
1066 After running or resetting a metric result, the details pane status is not updated.
1080 After resetting all metric results, the Details pane status is not updated
1084 Emissions PM calculation is not accounting for runway end elevation offset from airport
reference elevation
1085 Emissions rollup in AMM is not accounting for runway end elevation offset from airport
reference elevation

28
Aviation Environmental Design Tool
21949 Copying an aircraft in GUI does not copy the rows from the [FLT_ANP_AIRPLANE_NPD_CURVES]
table
22326 Enable Geospatially Referenced Ambient option in GUI for TALA metric
22431 After copying operating configuration, capacity values of new config are displayed for original
config in Details pane
22468 Replace "First Day" column label in grids with "Operation Time"
22509 Visualization issues in Flight performance graph when running with DSQM
22517 Rename the Ambient label in Definitions tab, Terrain & Ambient screen
22522 Metric result with profile-based ops created in GUI + DSQM generates two events per air op
22538 When helicopter is copied in GUI, data from [FLT_ANP_HELICOPTER_DIRECTIVITY] table are not
copied
22552 Exception generated when the Airport Edit button is clicked for airport layout
22559 In Partial ASIF import dialog, a grid receptor set type is incorrectly displayed as point
22565 Correct typo and misleading "GSE LTO" label in Create Aircraft Operation wizard
22010 Cannot update the capacity frontier values of existing operating configuration
22038 AEDT crashes after error encountered importing NMPlot grid file
22044 Flight performance report throws exception in aedt.log if a metric result contains GSE
population
22195 OM: Exception thrown in aedt.log when airport's pressure, humidity, and dew point are all NULL
22243 In Airports tab, the bottom grid for operating configuration shows data from airport/airport
layout
22246 Unhandled exception when you reduce the height of bottom workspace in Airports tab
22279 Validation check error in Contour Settings dialog
22293 OM: Editing track properties in Edit Track dialog does not save
22430 No values are displayed in Activation Parameters step when editing existing operating
configuration
22391 TerrainGlobalMapper.dll is not installed for distributed processing
22402 Fix folder/file browser in Definitions tab.
21347 UX bug: Clicking cancel in Definitions tab, Weather does not reset to original values
21363 UX bug: selecting a folder for the High fidelity weather data directory does not work
22387 Creating profile-based air operations in GUI does not set the runway end in AIR_OPERATION
table
22389 Creating profile-based air operations in GUI does not expand the ops to be unique (op_count=1)
22425 OM: GSE operations of type "Lift" crash when running
22247 Inaccurate error message regarding receptor set size when running detailed noise
22106 When creating air op, GSE assignments are not saved if the aircraft does not have default GSEs
in [FLT_GSE_AC_DEFAULTS] table
22274 Issue with the Copy of the operations with GSE LTO
22050 "TGO profile is larger than TGO track" exception is thrown for trivial difference
21157 Emissions report shows descend emissions for a helicopter departure
22153 Update Operations Group Summary to include Helo GroundIdle segments
21984 Boiler/Space Heaters that use LPG have incorrect unit for fuel sulfur content in GUI

Known Issues
1. Some airframe/engine combinations from EDMS 5.1.4.1 system data are incongruent with AEDT 2b
and are reported “bad data integrity” errors during EDMS study import. To correct, import the
aircraft as user-defined aircraft. (21179)
2. When an EDMS study containing grid receptor sets is converted to AEDT, the rendering of receptor
locations will be slightly mismatched between EDMS and AEDT. This is because in AEDT the origin of
29
Aviation Environmental Design Tool
the grid receptor is in the bottom left corner, while EDMS uses the offsets based on the center of
the grid. A workaround is to:
1) Incorporate the grid and the discrete receptors in the EDMS study into an AERMOD.INC file.
2) In AEDT 2b, go to Study tab, Preferences, Emissions Dispersion.
3) Check the “Use AERMOD receptor grid” option and reference the .INC file from step 1 in the
“File with AERMOD receptor grid” option. This makes the application ignore the receptor set
assigned to the emissions dispersion metric result, and forces using the specified AERMOD grid
receptor. The INC file can contain both grid and discrete receptors.
3. Flight profiles are not editable when creating a user-defined aircraft in Equipment tab. Use ASIF
import in order to create a new aircraft with different flight profiles. (21323)
4. Deleting user-defined helicopter is not supported in the Equipment tab. (21169)
5. Flight performance report and emissions report for helitaxi operations do not correctly reflect
inbound vs. outbound operation type.
6. Opening multiple emissions reports may show data from a different report. To avoid this issue, open
only one emissions report at a time. (21322)
7. In the INM to ASIF Converter tool, the “Enable User Defined Airport” option is not supported.
(21333)
8. In the Speciated Organic Gases tab in the Emissions Report, repeatedly converting units may
produce inconsistent values in the report. (21329)
9. Unhandled exception is generated when opening a study originally created on a different install
location with the default base map. (21103)
10. Generating noise contour for imported metric result is not supported. To examine results, view the
receptor set. (21335)
11. A helitaxi track imported via ASIF will be listed in the Airports Details pane, however it will not be
displayed on the map as part of the airport layout layer. To view the helitaxi track on map, view
tracks in the Metric Results tab. (21029)
12. After a partial ASIF import, the application does not refresh. Restart the application to view the
imported data. (21293)
13. If you get a “timeout expired” error when generating an emissions report, a workaround is to:
1) In Study tab, Database Preferences, increase the “Datacontext timeout” setting (e.g. 300
seconds).
2) Generate the “Operation Summary” emissions report first.
3) Generate the “Operation Group Summary” emission report.
14. User settings from prior installations may not be removed exhibiting behavior such as failed contour
generation (old filename for contouring gpk). Manually delete the file C:\AEDT\DATA\[User
name]\user_settings.json where [User name] is the Windows account name under which the user is
working.
15. Uninstalling AEDT when another application is connected to the AEDT databases leaves any
connected databases on the server. As a workaround, delete the databases manually using
Microsoft SQL Server Management Studio. (12194)
16. After closing a study in the AEDT application, Microsoft SQL Server still maintains a connection to
the database for several minutes. To delete a study database, exit from the AEDT application first;
then delete the desired database in the Microsoft SQL Server Management Studio. (18027)
17. An apostrophe in the study name is not supported (e.g. O’Hare). The Open Study dialog will display
“Can't connect to the database server because either the server is down or username and password
are incorrect” error if a study name contains apostrophe. (21454)
18. Aircraft equipment groups cannot be used to assign tracks to operations. User’s only access to
Operation Group Percent Distribution processing is through direct SQL injection of AIR_OPERATION
table. (21921)
30
Aviation Environmental Design Tool
19. Airports with an expiration date set to a past date may not import via ASIF. A workaround is to
change the expiration date in the Airports database.
20. The INM to ASIF Converter will not convert system aircraft with user modified properties (i.e. added
a custom profile, but still used the same system aircraft name). A workaround is to rename the
aircraft with a unique name so that the Converter recognizes it as a user-defined aircraft.
21. Weather import does not take into account Airport Layout Start date. Manually confirm that the
dates for weather data being used are after the start date of the associated airport layout. (8386)
22. Sensor path tracks cannot be rendered in the map display. As a workaround, in the Flight
Performance Report view the Flight Segments tab for an operation using the sensor path track.
(13236)
23. Flight operations specifying cruise altitude above the highest allowable specified aircraft altitude are
processed. Manually confirm cruise altitude on the operation against the BADA cruise altitude limit.
(6676)
24. Processing of high fidelity weather data is not thread-safe. To compensate, set the
“NumberOfThreads” key to 1 in C:\Program
Files\FAA\AEDT\FAA.AEE.AEDT.GUI.View.Ribbon.exe.config file. (21287)
25. If the BADA energy share factor is not present in the FLT_ANP_BADA_ENERGYSHARE table for the
aircraft's ANP ID/BADA ID combination, it can cause an infinite loop when processing such aircraft.
The BADA energy share factor is used in modeling the transition from the ANP flight regime for the
terminal area and the BADA flight regime for the cruise portion of the flight. A workaround is to
manually insert a record into this table. (21954)
26. Noise metric results using dynamic grid receptor sets will not be processed when airport codes are
user-defined. As a workaround, temporarily reassign the user-define airport code to an ICAO code.
(21339)
27. “Unable to upgrade study” error will be displayed during the study upgrade process if a study
contains a non-aircraft equipment group. Delete the non-aircraft equipment groups from a study
before upgrading it. (22077)
28. AEDT is unable to process 3CD terrain files. A workaround is to use GridFloat files instead. (22045)
29. ASIF import does not populate the taxi in/out time columns in the AIR_OPERATION table. (21976)
30. The noise grid file exported from AEDT is incorrectly scaled. (21963)
31. An AEDT generated shapefile cannot be imported into Google Earth Pro. (21979)
32. Taxi-gate intersection location calculation is incorrect. (22008)
33. Taxi network runways use the default runway width (20 meters) instead of the defined runway
width. (22007)
34. Deleting a taxipath is not supported if a study has been already run. (22041)
35. When exporting some aircraft from the Equipment tab, only the STANDARD profiles are included,
not ICAO-A and ICAO-B.(22073)
36. Noise contours may be displaced on the map (i.e. does not align with the receptor set) if the X and Y
spacings are not the same. (22072)
37. User’s only access to Operation Group Percent Distribution processing is through direct SQL
injection of AIR_OPPERATIONS.
38. The “Height above terrain – offset from elevation (ft)” field in the Definitions tab, user provided
receptor height is not used for noise or emissions dispersion processing. (1346)
39. When applying Delay & Sequencing, air operations based on operational profiles with “Operation
Count” values that are small, e.g. less than one operation per scenario duration, are subject to a
quantization error in the assignment of the operation time.
40. Military aircraft runup operations are not supported in AEDT 2b. (22175)
41. User-defined helicopters and user-defined military aircraft in an INM study are not converted by the
INM to ASIF Converter Tool. (22242)
31
Aviation Environmental Design Tool
42. When an INM study containing grid receptor sets is converted to AEDT, receptor locations will be
slightly mismatched between INM and AEDT. This is because in INM, the origin of the grid receptor
is offset from the projection origin (the airport origin). In AEDT, the projection origin (airport origin)
is treated as the grid origin. (511)
43. In order to use different Terrain files in the same study, restart AEDT after changing the Terrain
directory. (1388)
44. In order to use different ambient files in the same study, restart AEDT after changing ambient
files/directory. (1389)

Release AEDT 2b SP2


Release Date: December 22, 2015
Installer Size: 443 MB
Revision: 62.3.43407.1
Database Revisions:
• AIRPORT v2.15.0
• FLEET v3.20.2
• STUDY v1.43.2

This AEDT 2b Service Pack 2 (SP2) includes several bug fixes and updates since the AEDT 2b release in
May 2015. A full list of bug fixes and updates is listed below.

Instructions on how to install AEDT 2b SP2 or update to SP2 from an existing release of AEDT 2b can be
found in Section 5.2 of the Installation Guide.

New Features
1. Updated STUDY to v1.43.2 (fixed incorrect emissions indices in non-ICAO engines).
2. Updated FLEET to v3.20.2 (fixed incorrect emissions indices in non-ICAO engines).
3. Population exposure report enhancement
• Supports all noise metrics, not just DNL.
• No longer requires the user to generate a contour before creating a population exposure report.
• Uses the contour options in the Study tab, Preferences screen.
4. Added the new Dynamic Grid settings to Study Preferences screen (used to be in app.config).
5. Added the new Database preference to the Study tab, Preferences screen.

Warnings
1. When installing AEDT, if you wish to save any user modifications to AEDT system databases
(STUDY_XXXX, AIRPORT, or FLEET), perform a manual backup of the databases before uninstalling
the prior release of AEDT.
2. Existing user-created studies need to be upgraded to the current release in order to use them in
AEDT 2b SP2.
3. AEDT supports upgrading studies that are one release prior to the current release via Study tab >
Open > Show All Versions checkbox.
a) It is strongly recommended to select the “Backup study and upgrade” option to preserve a copy
of the existing study database before upgrading.
b) If the upgrade process fails, the study database could be corrupted and can only be restored
from a backup file.

32
Aviation Environmental Design Tool
c) After upgrading a user-defined study, reset and re-run the existing metric results in the study.
4. Conversion of AEDT 2a studies to AEDT 2b is supported through the stand-alone AEDT 2a to 2b
converter.
5. If you get the following errors when starting AEDT after installing AEDT 2b SP2, follow the steps
below.
• Exception 1: System.ComponentModel.Win32Exception (0x80004005): The system cannot find
the file specified
• Exception 2: System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-
specific error occurred while establishing a connection to SQL Server. The server was not found
or was not accessible. Verify that the instance name is correct and that SQL Server is configured
to allow remote connections.

Workaround steps:
a) Uninstall AEDT and make sure that the C:\AEDT folder is deleted.
b) Restart the computer.
c) Install the AEDT 2b SP2 again.

Resolved Issues
Item ID Description
22083 Inconsistent emissions results when repeat runs with “Calculate Aircraft Engine Startup
Emissions” option
22078 Helicopter runway end (Helipad) adjustment is not done with terrain
22055 Incorrect EIs in non-ICAO Fleet Engines
21983 Upgraded TerrainGlobalMapper.dll for new licensing structure
21957 Added missing TerrainGlobalMapper.dll file to distributed processing installer
21476 APU Emissions are not generated if there is no gate assignment
21304 Selecting the Startup Emissions checkbox in Study Preferences selects the "Calculate speciated
organic gases" checkbox in Set Processing Options screen
43321 Bug fix in importing TOG from MOVES inventory file.
43311 Bug fix in Save as Shapefile feature.
43306 Bug fix for the Use Bank Angle option in GUI.
43286 Bug fix for handling large amount of air operations in Create Annualization wizard.
43285 Bug fix for mixing height value in ASIF import.
43279 Fixed an issue with intersecting taxipaths in airport layout designer.
43269 Bug fix for LAEQD contour generation
43241 Error logging for speciated hydrocarbon handling in the emissions reports.
43232 Bug fix for GUI management on first start-up of the GUI.
43193 Bug fix in emissions report handling of operation count (APU and GSE LTO emissions).
43192 Generate layers for multiple results at once.
43177 Bug fix to Get Operations selector in the Metric Results tab and Operations tabs.
43158 Visual aid for cancelled/failed Get Operations function.
43129 Mechanism implemented to control significant digits by app.config tag.
43100 Added logging to indicate which refinement algorithm is used for Dynamic Grids.
43072 Bug fixed in the dynamic grid algorithm for complex track structure.
43042 Added a check for null gate properties.
42998 Internal data flow for operations processing module under group percent distributions
42980 Fixed the Dynamic Grid process to support execution of multiple metric results.
42972 Bug fix on a process control variable for terrain and computational performance speed up on
DSQM
33
Aviation Environmental Design Tool
42968 Improved EDM process logging
42811 Changed the default PM model to PM 3.0a.
42787 Computational performance improvement on results loading for emissions reports.
42677 Improved the logging and error reporting on emissions report generation.
42612 EDM weather (ASOS) time index bug from EDMS method corrected.
42601 Bug fix to EDMS treatment of weather data (ASOS). [EDM Weather Data Loader]
42502 Reconciled taxi emissions bins with EDMS
42248 RunStudy command-line tool now supports running emissions dispersion metric result
42191 Added the Calculate speciated organic gases checkbox to Study tab, Preferences screen
42190 Flight performance report improvement, added a new column
42143 Bug fix in adding a new building during airport layout design.
42093 Improved rendering of annualization tree in the Create Annualization wizard.
42086 Improved the log display function to auto scroll as new entries are added.

Known Issues
1. Some airframe/engine combinations from EDMS 5.1.4.1 system data are incongruent with AEDT 2b
and are reported “bad data integrity” errors during EDMS study import. To correct, import the
aircraft as user-defined aircraft. (21179)
2. When an EDMS study containing grid receptor sets is converted to AEDT, the rendering of receptor
locations will be slightly mismatched between EDMS and AEDT. This is because in AEDT the origin of
the grid receptor is in the bottom left corner, while EDMS uses the offsets based on the center of
the grid. A workaround is to:
1) Incorporate the grid and the discrete receptors in the EDMS study into an AERMOD.INC file.
2) In AEDT 2b, go to Study tab, Preferences, Emissions Dispersion.
3) Check the “Use AERMOD receptor grid” option and reference the .INC file from step 1 in the
“File with AERMOD receptor grid” option. This makes the application ignore the receptor set
assigned to the emissions dispersion metric result, and forces using the specified AERMOD grid
receptor. The INC file can contain both grid and discrete receptors.
3. Flight profiles are not editable when creating a user-defined aircraft in Equipment tab. Use ASIF
import in order to create a new aircraft with different flight profiles. (21323)
4. Deleting user-defined helicopter is not supported in the Equipment tab.
5. Editing emissions factors for user-defined GSE in the Equipment tab is not supported. Use ASIF
import in order to create new non-aircraft equipment with user-defined EIs. (21330)
6. Flight performance report and emissions report for helitaxi operations do not correctly reflect
inbound vs. outbound operation type.
7. The emissions report for helicopter departures is incorrect (i.e. results are reported for Descend
modes). (21157)
8. Opening multiple emissions reports may show data from a different report. To avoid this issue, open
only one emissions report at a time. (21322)
9. In the INM to ASIF Converter tool, the “Enable User Defined Airport” option is not supported.
(21333)
10. In the Speciated Organic Gases tab in the Emissions Report, repeatedly converting units may
produce inconsistent values in the report. (21329)
11. Unhandled exception is generated when opening a study originally created on a different install
location with the default base map. (21103)
12. Generating noise contour for imported metric result is not supported. To examine results, view the
receptor set. (21335)

34
Aviation Environmental Design Tool
13. A helitaxi track imported via ASIF will be listed in the Airports Details pane, however it will not be
displayed on the map as part of the airport layout layer. To view the helitaxi track on map, view
tracks in the Metric Results tab. (21029)
14. After partial ASIF import of annualization and userGroundSupportEquipmentSet, application does
not refresh. Restart the application to view the imported data. (21293)
15. If you get “timeout expired” error when generating emissions report, a workaround is to:
1) In Study tab, Database Preferences, increase the “Datacontext timeout” setting (e.g. 300
seconds).
2) Generate the “Operation Summary” emissions report first.
3) Generate the “Operation Group Summary” emission report.
16. User settings from prior installations may not be removed exhibiting behavior such as failed contour
generation (old filename for contouring gpk). Manually delete the file C:\AEDT\DATA\[User
name]\user_settings.json where [User name] is the Windows account name under which the user is
working.
17. Uninstalling AEDT when another application is connected to the AEDT databases leaves any
connected databases on the server. As a workaround, delete the databases manually using
Microsoft SQL Server Management Studio. (12194)
18. After closing a study in the AEDT application, Microsoft SQL Server still maintains a connection to
the database for several minutes. To delete a study database, exit from the AEDT application first;
then delete the desired database in the Microsoft SQL Server Management Studio. (18027)
19. Apostrophe in study name (e.g. O’Hare) is not supported. The Open Study dialog will display “Can't
connect to the database server because either the server is down or username and password are
incorrect” error if a study name contains apostrophe. (21454)
20. The Noise-Power-Distance (NPD) data are not copied when creating a user-defined aircraft in the
Equipment tab. Use ASIF import in order to create a new aircraft. (21949)
21. Aircraft equipment groups cannot be used to assign tracks to operations. (21921)
22. Airports with an expiration date set to a past date may not import via ASIF. A workaround is to
change the expiration date in the Airports database.
23. The INM to ASIF Converter will not convert system aircraft with user modified properties (i.e. added
a custom profile, but still used the same system aircraft name). A workaround is to rename the
aircraft with a unique name so that the Converter recognizes it as a user-defined aircraft.
24. Weather import does not take into account Airport Layout Start date. Manually confirm that the
dates for weather data being used are after the start date of the associated airport layout. (8386)
25. Sensor path tracks cannot be rendered in the map display. As a workaround, in the Flight
Performance Report view the Flight Segments tab for an operation using the sensor path track.
(13236)
26. Flight operations specifying cruise altitude above the highest allowable specified aircraft altitude are
processed. Manually confirm cruise altitude on the operation against the BADA cruise altitude limit.
(6676)
27. Processing of high fidelity weather data is not thread-safe. To compensate, set the
“NumberOfThreads” key to 1 in C:\Program
Files\FAA\AEDT\FAA.AEE.AEDT.GUI.View.Ribbon.exe.config file. (21287)
28. If the BADA energy share factor is not present in the FLT_ANP_BADA_ENERGYSHARE table for the
aircraft's ANP ID/BADA ID combination, it can cause infinite loop when processing such aircraft. The
BADA energy share factor is used in modeling the transition from the ANP flight regime for the
terminal area and the BADA flight regime for the cruise portion of the flight. A workaround is to
manually insert a record into this table. (21954)

35
Aviation Environmental Design Tool
29. User-defined airport codes will not be processed for noise metric results using dynamic grid
receptor sets. As a workaround temporarily reassign the user-define airport code to an ICAO code.
(21339)
30. “Unable to upgrade study” error will be displayed during the study upgrade process, if a study
contains a non-aircraft equipment group. Delete the non-aircraft equipment groups from a study
before upgrading it. (22077)
31. AEDT is unable to process 3CD terrain files. A workaround is to use GridFloat files instead. (22045)
32. "TGO profile is larger than TGO track" exception can occur for trivial difference in track and profile
length. (22050)
33. Generating noise exposure report is not supported for user-defined noise metrics. (22051)
34. Flight performance report throws exception in aedt.log if a metric result contains GSE population.
(22044)
35. The "Num Ops" column in Emissions report (Operations Detail) shows 0 if value is less than 0.1.
(21952)
36. ASIF import does not populate the taxi in/out time columns in the AIR_OPERATION table. (21976)
37. ASIF export of helicopter does not contain data from the FLT_ANP_HELICOPTER_PROCEDURES table.
(21955)
38. Importing a binary format NMPlot grid file generated from INM results in an unhandled exception
and closes AEDT. (22038)
39. Noise grid file exported from AEDT is incorrectly scaled. (21963)
40. AEDT generated shapefile cannot be imported into Google Earth Pro. (21979)
41. The capacity frontier values of existing operating configuration cannot be updated. (22010)
42. Taxi-gate intersection location calculation is incorrect. (22008)
43. Taxi network runways use default runway width (20 meters) instead of the defined runway width.
(22007)
44. Deleting a taxipath is not supported if a study has been already run. (22041)
45. Adding/deleting points in the Edit Taxiway dialog is not supported. (22040)
46. The Initial Sigma-Y field should be disabled in the Edit Terminal dialog. (21994)
47. The Boiler/Space Heaters that use LPG have incorrect unit for fuel sulfur content in GUI. (21984)
48. The “Height AFE (ft)” field for non-aircraft operations (i.e. STN_OP table, ELEVATION field) should
say meters instead of feet. (21985)
49. In Equipment tab, Non-Aircraft view, the labels for "Other" stationary source are incorrect. (21966)
50. The "Maximum Liquid Height" should be displayed for vertical types of Fuel Tank and not for
horizontal types. (21975)
51. In Definitions tab, selecting a folder for the High fidelity weather data directory does not work. Users
have to copy and paste the folder path instead. (21363)
52. "Unable to upgrade study" error will be displayed during study upgrade process, if a study contains
non-aircraft equipment group. (22077)
53. Exporting some aircraft from the Equipment tab only includes the STANDARD profiles and not ICAO-
A and ICAO-B. (22073)
54. Noise contours may be displaced on the map (i.e. does not align with the receptor set) if the X and Y
spacings are not the same. (22072)
55. User’s only access to Operation Group Percent Distribution processing is through direct SQL
injection of AIR_OPPERATIONS.
56. The “Height above terrain – offset from elevation (ft)” field in the Definitions tab, user provided
receptor height is not used for noise or emissions dispersion processing.
57. When applying Delay & Sequencing, air operations based on operational profiles with “Operation
Count” values that are small, e.g. less than one operation per scenario duration, are subject to
quantization error in the assignment of the operation time.
36
Aviation Environmental Design Tool
Release AEDT 2b FP1
Release Date: July 28, 2015
Installer Size: 441 MB
Revision: 62.1.42691.1
Database Revisions:
• AIRPORT v2.15.0
• FLEET v3.20.1
• STUDY v1.43.1

This AEDT Feature Pack (FP) update serves only as an update to the pair of third-party tools for
processing emissions dispersion metric results. The EPA tools addressed are AERMOD (updated from
Ver 12345 to 14134) and AERMET (also updated from ver 12345 to 14134).

Notation and AEDT support documents (Installation Guide and User Guide) have also been updated to
match appropriate EPA versions. All system and demonstration databases remain the same as the prior
release.

Warnings
• When installing AEDT, if you wish to save any user modifications to AEDT provided databases
STUDY_XXXX, AIRPORT, or FLEET databases, perform a manual backup of the databases before
uninstalling the prior release of AEDT.
• Any user created studies, e.g. Study > New or Study > Open > Open from ASIF will not be affected by
the installation.
• AEDT 2b supports integrated upgrading of studies from the prior release via Study > Open > Show All
Versions. Conversion of AEDT 2a studies to AEDT 2b is supported through the stand-alone AEDT 2a
to 2b converter.

Resolved Issues
Item ID Description
21390 Emissions dispersion weather processing of data extending beyond the dates included in the
metric result duration is now filtered to the metric result duration dates to address the AERMOD
constraint that input weather days must match the source emissions days.
21391 Emissions dispersion weather processing was not able to handle SCRAM (older external format)
external weather data which was based on airport local time. Said weather data file times are
now handled properly.

Known Issues
1. Some airframe/engine combinations from EDMS 5.1.4.1 system data are incongruent with AEDT 2b
and are reported “bad data integrity” errors during EDMS study import.
2. When an EDMS study containing grid receptor sets is converted to AEDT, the rendering of receptor
locations will be slightly mismatched between EDMS and AEDT.
3. Flight profiles are not editable when creating a user-defined aircraft in Equipment tab. Use ASIF
import in order to create a new aircraft with different flight profiles.
4. Deleting user-defined helicopter is not supported in the Equipment tab.
5. Editing emissions factors for user-defined GSE in the Equipment tab is not supported. Use ASIF
import in order to create new non-aircraft equipment with user-defined EIs.
6. Flight performance report and emissions report for helitaxi operations do not correctly reflect
inbound vs. outbound operation type.
37
Aviation Environmental Design Tool
7. Emissions report for helicopter departures is incorrect (i.e. results are reported for Descend modes).
8. Opening multiple emissions reports may show data from a different report. To avoid this issue, open
only one emissions report at a time.
9. In the INM to ASIF Converter tool, the “Enable User Defined Airport” option is not supported.
10. In the Speciated Organic Gases tab in the Emissions Report, repeatedly converting units may
produce inconsistent values in the report.
11. Unhandled exception is generated when opening a study originally created on a different install
location with the default Base Map.
12. Generating noise contour for imported metric result is not supported. To examine results, View
Receptor Set.
13. A helitaxi track imported via ASIF will be listed in the Airports Details pane, however it will not be
displayed on the map as part of the airport layout layer. To view the helitaxi track on map, view
tracks in the Metric Results tab.
14. If a building added in airport layout designer has successive location points with either the same
latitude or longitude, that location point is not saved.
15. After partial ASIF import of annualization and userGroundSupportEquipmentSet, application does
not refresh. Restart the application to view the imported data.
16. For studies generating emissions results that include GSE or APU contributions, the report function
for operational or segment levels results on large operation groups will time out, sometimes silently.
To work around the issue until fixed, split groups containing GSE or APU content into smaller sets.
17. Aircraft models using the following set of non-ICAO EDB listed engines should not be used. Errant
CO emissions indices for those engines will be fix in the next Fleet database update.
250B17
501D22
6285B
CF700D
CJ6102
IO320
IO360
J57P22
J65W20
J7910
J8521
J855F
JT9D70
O200
O320
RB524
TF306B
TF3333
TF391
TIO540
TPE2
TPE3
TSIO36
TYNE
MK555

38
Aviation Environmental Design Tool
Release AEDT 2b
Release Date: May 29, 2015
Installer Size: 441 MB
Revision: 62.0.42218.1
Database Revisions:
• AIRPORT v2.15.0
• FLEET v3.20.1
• STUDY v1.43.1

Warnings
• When installing AEDT, if you wish to save any user modifications to AEDT provided databases
STUDY_XXXX, AIRPORT, or FLEET databases, perform a manual backup of the databases before
uninstalling the prior release of AEDT.
• Any user created studies, e.g. Study > New or Study > Open > Open from ASIF will not be affected by
the installation.
• AEDT 2b supports integrated upgrading of studies from the prior release via Study > Open > Show All
Versions. Conversion of AEDT 2a studies to AEDT 2b is supported through the stand-alone AEDT 2a
to 2b converter.

Known Issues
1. Some airframe/engine combinations from EDMS 5.1.4.1 system data are incongruent with AEDT 2b
and are reported “bad data integrity” errors during EDMS study import.
2. When an EDMS study containing grid receptor sets is converted to AEDT, the rendering of receptor
locations will be slightly mismatched between EDMS and AEDT.
3. Flight profiles are not editable when creating a user-defined aircraft in Equipment tab. Use ASIF
import in order to create a new aircraft with different flight profiles.
4. Deleting user-defined helicopter is not supported in the Equipment tab.
5. Editing emissions factors for user-defined GSE in the Equipment tab is not supported. Use ASIF
import in order to create new non-aircraft equipment with user-defined EIs.
6. Flight performance report and emissions report for helitaxi operations do not correctly reflect
inbound vs. outbound operation type.
7. Emissions report for helicopter departures is incorrect (i.e. results are reported for Descend modes).
8. Opening multiple emissions reports may show data from a different report. To avoid this issue, open
only one emissions report at a time.
9. In the INM to ASIF Converter tool, the “Enable User Defined Airport” option is not supported.
10. In the Speciated Organic Gases tab in the Emissions Report, repeatedly converting units may
produce inconsistent values in the report.
11. Unhandled exception is generated when opening a study originally created on a different install
location with the default Base Map.
12. Generating noise contour for imported metric result is not supported. To examine results, View
Receptor Set.
13. A helitaxi track imported via ASIF will be listed in the Airports Details pane, however it will not be
displayed on the map as part of the airport layout layer. To view the helitaxi track on map, view
tracks in the Metric Results tab.
14. If a building added in airport layout designer has successive location points with either the same
latitude or longitude, that location point is not saved.
15. After partial ASIF import of annualization and userGroundSupportEquipmentSet, application does
not refresh. Restart the application to view the imported data.
39

Вам также может понравиться