37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1298523 |
Time | |
Date | 201509 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | HRJ.Airport |
State Reference | NC |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 50 Flight Crew Total 8000 Flight Crew Type 5000 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Hrj does not have a ground frequency to receive a clearance from fayetteville approach. When the airport is IFR; the best method suggested by the FBO was to call TRACON on a cellphone. I did this at about XA00Z and was told they could not give me a clearance due to traffic and to call back in 10 minutes. I did; and after a short delay I was given a clearance. There was background talking going on and it seemed the controller was talking to someone else prior to giving my clearance. I wrote the clearance down and read it back. I was told clearance read back was correct. (Aircraft north#) is cleared to 3000; expect 7000 and as filed after airborne. Squawk 3624; clearance starts XA25; if not airborne by XA35; call ATC. We began our takeoff roll at XA25 and called ATC within a minute.we contacted ATC; were asked to ident; were radar identified; and given a clearance to our destination as filed and cleared to 7000. After being handed off to rdu approach; we were informed fayetteville requested a phone call. We called upon arrival and were informed we had missed our clearance time and not gone to an intersection provided in the clearance. I informed the person that I had read back the clearance I understood and was told it was correct. He indicated he just wanted me to know what to expect in the future when operating in and out of the airport.I believe there was confusion on clearance times and I do not recall hearing the intersection; perhaps due to the background discussion/talking. That confusion may have led to the controller thinking I read back what he said when I didn't. A cellphone in the cockpit is not an effective communication tool. There should be a ground frequency available to talk directly to ATC is a discrete way. In the future I will avoid picking up clearances by phone if at all possible and I will read back the clearance very deliberately to make sure we are all on the same page. I suggest ATC have a method to make the phone call with no background noise; and where at all possible ATC have a ground transmission/receiver capability.
Original NASA ASRS Text
Title: General aviation pilot departing HRJ; reported getting his IFR clearance from Fayetteville Approach via cell phone. There was a great deal of background noise on the call and the clearance was apparently not copied correctly; although the read back was accepted. After takeoff the reporter was informed that he skipped the first fix and departed at the wrong time. HRJ has no VHF Clearance Delivery capability.
Narrative: HRJ does not have a ground frequency to receive a clearance from Fayetteville Approach. When the airport is IFR; the best method suggested by the FBO was to call TRACON on a cellphone. I did this at about XA00Z and was told they could not give me a clearance due to traffic and to call back in 10 minutes. I did; and after a short delay I was given a clearance. There was background talking going on and it seemed the controller was talking to someone else prior to giving my clearance. I wrote the clearance down and read it back. I was told clearance read back was correct. (aircraft N#) is cleared to 3000; expect 7000 and as filed after airborne. Squawk 3624; clearance starts XA25; if not airborne by XA35; call ATC. We began our takeoff roll at XA25 and called ATC within a minute.We contacted ATC; were asked to ident; were radar identified; and given a clearance to our destination as filed and cleared to 7000. After being handed off to RDU approach; we were informed Fayetteville requested a phone call. We called upon arrival and were informed we had missed our clearance time and not gone to an intersection provided in the clearance. I informed the person that I had read back the clearance I understood and was told it was correct. He indicated he just wanted me to know what to expect in the future when operating in and out of the airport.I believe there was confusion on clearance times and I do not recall hearing the intersection; perhaps due to the background discussion/talking. That confusion may have led to the controller thinking I read back what he said when I didn't. A cellphone in the cockpit is not an effective communication tool. There should be a ground frequency available to talk directly to ATC is a discrete way. In the future I will avoid picking up clearances by phone if at all possible and I will read back the clearance very deliberately to make sure we are all on the same page. I suggest ATC have a method to make the phone call with no background noise; and where at all possible ATC have a ground transmission/receiver capability.
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.