37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1251746 |
Time | |
Date | 201504 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | DAB.TRACON |
State Reference | FL |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Departure |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 12 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Aircraft X departed dab on an IFR flight plan. Lam was in the scratch pad; this leads the controllers to believe the aircraft is a lamma departure. The aircraft was told to proceed direct lamma intersection. The aircraft then asked what do I do after lamma. The aircraft was an ilind departure and should have had ild in the scratch pad area on his data tag. This is something that I have sent reports in several times over the last few years and have sent to our automation specialist several times.the aircraft penetrated F11 airspace prior to coordination in the wrong location. This error belongs to the reporting program and dab automation for non-action on known problems.fix the scratch pads on departures to show the correct departure gate!
Original NASA ASRS Text
Title: DAB Controller reports of an automation problem with the wrong scratch pad information showing up in aircraft data block. This lead to confusion for the Controller; pilot and resulted in an airspace deviation.
Narrative: Aircraft X departed DAB on an IFR flight plan. LAM was in the scratch pad; this leads the controllers to believe the aircraft is a LAMMA departure. The aircraft was told to proceed direct LAMMA intersection. The aircraft then asked what do I do after LAMMA. The aircraft was an ILIND departure and should have had ILD in the scratch pad area on his data tag. This is something that I have sent reports in several times over the last few years and have sent to our automation specialist several times.The aircraft penetrated F11 airspace prior to coordination in the wrong location. This error belongs to the reporting program and DAB automation for non-action on known problems.Fix the scratch pads on departures to show the correct departure gate!
Data retrieved from NASA's ASRS site 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.