 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-200 first officer notes the crossing DME mileage is not given on the lizard two STAR into tpa at marvi intersection.
| Attributes | |
| ACN | 572543 |
| Time | |
| Date | 200301 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | intersection : marvi |
| State Reference | FL |
| Altitude | msl single value : 13000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dawn |
| Aircraft 1 | |
| Controlling Facilities | artcc : zjx.artcc |
| Operator | common carrier : air carrier |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | descent : approach |
| Route In Use | arrival star : lzard 2 |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 220 flight time total : 3400 flight time type : 700 |
| ASRS Report | 572543 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : anomaly accepted other |
| Supplementary | |
| Problem Areas | Chart Or Publication |
| Primary Problem | Chart Or Publication |
| Situations | |
| Chart | star : tpa lizard two |
| Publication | Commercial Chart |
Narrative:
Confusing arrival chart tpa lizard 2 STAR. On lizard 2 arrival to tpa, given marvi at 13000. Began descent based on DME from tay, with grasn at tay 90 DME, and marvi 23 NM beyond that. After turning onto the olf 185 radial at grasn, however, we searched in vain for a DME associated with marvi (which we were to cross at 13000). That would be an important piece of information to have immediately available. On the ground at tpa, we determined that the DME at marvi can be calculated from the information on the arrival chart (through it is not obvious where one needs to look to find it), and that we had, in fact, made the crossing restriction several miles early. In the 'heat of battle' on the relatively short jax tpa flight, we did not find the necessary data on the chart, and over half the pilots I've shown this to couldn't come up with the solution either. The commercial chart vendor should state the DME off olf at marvi on the tpa lizard 2 STAR not leave us to hunt for the clues to determine it for ourselves.
Original NASA ASRS Text
Title: B737-200 FO NOTES THE XING DME MILEAGE IS NOT GIVEN ON THE LIZARD TWO STAR INTO TPA AT MARVI INTXN.
Narrative: CONFUSING ARR CHART TPA LIZARD 2 STAR. ON LIZARD 2 ARR TO TPA, GIVEN MARVI AT 13000. BEGAN DSCNT BASED ON DME FROM TAY, WITH GRASN AT TAY 90 DME, AND MARVI 23 NM BEYOND THAT. AFTER TURNING ONTO THE OLF 185 RADIAL AT GRASN, HOWEVER, WE SEARCHED IN VAIN FOR A DME ASSOCIATED WITH MARVI (WHICH WE WERE TO CROSS AT 13000). THAT WOULD BE AN IMPORTANT PIECE OF INFO TO HAVE IMMEDIATELY AVAILABLE. ON THE GND AT TPA, WE DETERMINED THAT THE DME AT MARVI CAN BE CALCULATED FROM THE INFO ON THE ARR CHART (THROUGH IT IS NOT OBVIOUS WHERE ONE NEEDS TO LOOK TO FIND IT), AND THAT WE HAD, IN FACT, MADE THE XING RESTRICTION SEVERAL MILES EARLY. IN THE 'HEAT OF BATTLE' ON THE RELATIVELY SHORT JAX TPA FLT, WE DID NOT FIND THE NECESSARY DATA ON THE CHART, AND OVER HALF THE PLTS I'VE SHOWN THIS TO COULDN'T COME UP WITH THE SOLUTION EITHER. THE COMMERCIAL CHART VENDOR SHOULD STATE THE DME OFF OLF AT MARVI ON THE TPA LIZARD 2 STAR NOT LEAVE US TO HUNT FOR THE CLUES TO DETERMINE IT FOR OURSELVES.
Data retrieved from NASA's ASRS site as of July 2007 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.