 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Montgomery tower controller reported a runway conflict after clearing an aircraft for takeoff while another aircraft was on short final.
| Attributes | |
| ACN | 1574647 |
| Time | |
| Date | 201809 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | MYF.Tower |
| State Reference | CA |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Landing |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Super King Air 200 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Landing Taxi |
| Route In Use | None |
| Flight Plan | VFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Critical |
Narrative:
Aircraft X was doing touch and goes on runway 28R. Aircraft X mode C was inoperative and I advised the pilot numerous times that his mode C was inoperative. During the final approach for aircraft X; aircraft Y called for IFR release. I received IFR release for aircraft Y. Aircraft X was over the displaced threshold and I cleared aircraft Y for takeoff. As aircraft Y was taking runway 28R for departure he asked if he was still clear for takeoff; because an aircraft landed in front of him down the runway. I cancelled aircraft Y takeoff clearance and issued luaw (line up and wait) instructions for aircraft Y. Aircraft X did not report/say anything; taxied to parking. I then cleared aircraft Y for takeoff. I believe aircraft X was obscured from my scan by a post in the tower cab window when the event occurred.I believe that a lack of traffic lead to complacency. I think that being more vigilant and cautious in my scan could have prevented this; especially when an aircraft was having problems with the mode C; and radar was inaccurate.
Original NASA ASRS Text
Title: Montgomery Tower Controller reported a runway conflict after clearing an aircraft for takeoff while another aircraft was on short final.
Narrative: Aircraft X was doing touch and goes on runway 28R. Aircraft X Mode C was inoperative and I advised the pilot numerous times that his Mode C was inoperative. During the final approach for Aircraft X; Aircraft Y called for IFR release. I received IFR release for Aircraft Y. Aircraft X was over the displaced threshold and I cleared Aircraft Y for takeoff. As Aircraft Y was taking runway 28R for departure he asked if he was still clear for takeoff; because an aircraft landed in front of him down the runway. I cancelled Aircraft Y takeoff clearance and issued LUAW (Line Up and Wait) instructions for Aircraft Y. Aircraft X did not report/say anything; taxied to parking. I then cleared Aircraft Y for takeoff. I believe Aircraft X was obscured from my scan by a post in the Tower cab window when the event occurred.I believe that a lack of traffic lead to complacency. I think that being more vigilant and cautious in my scan could have prevented this; especially when an aircraft was having problems with the Mode C; and radar was inaccurate.
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.