37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1428293 |
Time | |
Date | 201702 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Cessna 210 Centurion / Turbo Centurion 210C 210D |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Route In Use | Direct |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | King Air C90 E90 |
Flight Phase | Landing |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 12 Flight Crew Total 377 Flight Crew Type 193 |
Events | |
Anomaly | Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 0 Vertical 1000 |
Narrative:
I was departing on an instrument flight plan. I received my clearance from approach while parked at the FBO; and was told to hold short of runway 9. During taxi to runway 9; I was monitoring approach and CTAF simultaneously on separate radios. After stopping before the hold short markings for runway 9; I advised approach that I was number one for departure runway 9. Approach advised me that there was a king air on an instrument approach to runway 9; and cleared me for departure; 'void if not off in five minutes'. Although monitoring both frequencies; I overheard the king air calling final on the approach; but did not hear the distance. Because of the short void time; I incorrectly assumed that the king air was farther out and that I had a short time to depart. I switched frequencies and called a departure on runway 9 over the CTAF; and rolled past the hold short markings to begin takeoff. This transmission was quickly met with the king air pilot calling his position over the runway; and announcing his intention to go-around. I aborted takeoff and announced my intent to abort on CTAF; then contacted approach to relay this information.as PIC; I should have more closely monitored the position announcements of the king air. With this information; I would have waited for the king air to land; and still have been within my five minute void. In the future; I will request guidance from the controlling authority to clarify any vague information; and monitor CTAF frequencies at uncontrolled airports more closely.
Original NASA ASRS Text
Title: A C210 pilot reported a 5 minute clearance void time led to announcing takeoff intentions on the CTAF and hearing a King Air pilot announce a go around on short final.
Narrative: I was departing on an instrument flight plan. I received my clearance from Approach while parked at the FBO; and was told to hold short of Runway 9. During taxi to Runway 9; I was monitoring Approach and CTAF simultaneously on separate radios. After stopping before the hold short markings for Runway 9; I advised Approach that I was number one for departure Runway 9. Approach advised me that there was a King Air on an instrument approach to Runway 9; and cleared me for departure; 'void if not off in five minutes'. Although monitoring both frequencies; I overheard the King Air calling final on the approach; but did not hear the distance. Because of the short void time; I incorrectly assumed that the King Air was farther out and that I had a short time to depart. I switched frequencies and called a departure on Runway 9 over the CTAF; and rolled past the hold short markings to begin takeoff. This transmission was quickly met with the King Air pilot calling his position over the runway; and announcing his intention to go-around. I aborted takeoff and announced my intent to abort on CTAF; then contacted Approach to relay this information.As PIC; I should have more closely monitored the position announcements of the King Air. With this information; I would have waited for the King Air to land; and still have been within my five minute void. In the future; I will request guidance from the controlling authority to clarify any vague information; and monitor CTAF frequencies at uncontrolled airports more closely.
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.