 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-800 pilot reports the format for pre departure clearance delivered clrncs in mia are more subject to misinterp than those at dfw.
| Attributes | |
| ACN | 719614 |
| Time | |
| Date | 200612 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : mia.airport |
| State Reference | FL |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain |
| ASRS Report | 719614 |
| Events | |
| Resolutory Action | none taken : unable |
| Supplementary | |
| Problem Areas | Chart Or Publication FAA ATC Human Performance |
| Primary Problem | Chart Or Publication |
| Situations | |
| ATC Facility | procedure or policy : dfw.tower |
| Publication | DFW PDC Format |
Narrative:
This regards suggestion for standardized pre departure clearance clearance format. Dfw does it right. Mia does not; and invites deviations (which I've heard on departure frequency). Pre departure clearance should read departure airport followed by departure SID 'FMS' followed by routing; followed by arrival STAR; followed by arrival airport. Mia does not do this. They list the clearance as a series of points starting with the last point in the FMS SID; and in the notes on paragraph below is the SID; clearance altitude and notes. For example; mia used to do a miami runway 9 departure; hedley transition. Their clearance now just begins with hedley and the route; inviting someone to think they're doing the old miami runway 9 to hedley. Several operators have missed the note regarding the FMS departure and departed on a heading; not expecting vectors to hedley FMS fixes. Further; the routine practice of assigning a heading on takeoff invites obfuscation of the fact that an FMS departure routing has been assigned. Food for thought.
Original NASA ASRS Text
Title: B737-800 PLT RPTS THE FORMAT FOR PDC DELIVERED CLRNCS IN MIA ARE MORE SUBJECT TO MISINTERP THAN THOSE AT DFW.
Narrative: THIS REGARDS SUGGESTION FOR STANDARDIZED PDC CLRNC FORMAT. DFW DOES IT RIGHT. MIA DOES NOT; AND INVITES DEVS (WHICH I'VE HEARD ON DEP FREQ). PDC SHOULD READ DEP ARPT FOLLOWED BY DEP SID 'FMS' FOLLOWED BY ROUTING; FOLLOWED BY ARR STAR; FOLLOWED BY ARR ARPT. MIA DOES NOT DO THIS. THEY LIST THE CLRNC AS A SERIES OF POINTS STARTING WITH THE LAST POINT IN THE FMS SID; AND IN THE NOTES ON PARAGRAPH BELOW IS THE SID; CLRNC ALT AND NOTES. FOR EXAMPLE; MIA USED TO DO A MIAMI RWY 9 DEP; HEDLEY TRANSITION. THEIR CLRNC NOW JUST BEGINS WITH HEDLEY AND THE RTE; INVITING SOMEONE TO THINK THEY'RE DOING THE OLD MIAMI RWY 9 TO HEDLEY. SEVERAL OPERATORS HAVE MISSED THE NOTE REGARDING THE FMS DEP AND DEPARTED ON A HDG; NOT EXPECTING VECTORS TO HEDLEY FMS FIXES. FURTHER; THE ROUTINE PRACTICE OF ASSIGNING A HDG ON TKOF INVITES OBFUSCATION OF THE FACT THAT AN FMS DEP ROUTING HAS BEEN ASSIGNED. FOOD FOR THOUGHT.
Data retrieved from NASA's ASRS site as of January 2009 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.