37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 933318 |
Time | |
Date | 201102 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | BWI.Airport |
State Reference | MD |
Aircraft 1 | |
Make Model Name | EMB ERJ 145 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR EMI5 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Flight Instructor Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 180 Flight Crew Total 4000 Flight Crew Type 2200 |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Critical Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
The EMI5 arrival into bwi needs additional guidance past the EMI VOR. On several occasions while flying this arrival; potomac TRACON has failed to provide a vector prior to reaching EMI. Further complicating matters; the EMI VOR is programmed in the FMS database as a fly-by (rather than fly-over) waypoint. This causes the autopilot to initiate a turn prior to actually reaching EMI (and prior to receiving vectors from ATC in certain circumstances) if left to its own devices.no deviations have occurred on any flights I've worked as far as I know; but only thanks to the alertness of the crew and a quick switch of the flight guidance to heading mode; followed by querying ATC as to their intentions for us. It would seem to be much easier for everyone involved if: a) a vector (heading) after EMI was defined on the procedure; and b) EMI was made a fly-over waypoint (or left as a fly-by waypoint if appropriate; e.g. If the procedure were amended to require 'fly heading 150 after EMI').
Original NASA ASRS Text
Title: An E-145 First Officer suggested the EMI5 STAR at BWI be modified to provide a heading for vectors after passing the EMI VOR.
Narrative: The EMI5 arrival into BWI needs additional guidance past the EMI VOR. On several occasions while flying this arrival; Potomac TRACON has failed to provide a vector prior to reaching EMI. Further complicating matters; the EMI VOR is programmed in the FMS database as a fly-by (rather than fly-over) waypoint. This causes the autopilot to initiate a turn prior to actually reaching EMI (and prior to receiving vectors from ATC in certain circumstances) if left to its own devices.No deviations have occurred on any flights I've worked as far as I know; but only thanks to the alertness of the crew and a quick switch of the flight guidance to HDG mode; followed by querying ATC as to their intentions for us. It would seem to be much easier for everyone involved if: a) a vector (heading) after EMI was defined on the procedure; and b) EMI was made a fly-over waypoint (or left as a fly-by waypoint if appropriate; e.g. if the procedure were amended to require 'fly heading 150 after EMI').
Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.