![]()  | 
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. | 
		
			
  | 	
	
	
		
		|||||||
| 
		 | 
	Thread Tools | Display Modes | 
| 
		 
			 
			#1  
			 
            
			
			
			
		 
		
		
	 | 
|||
		
		
  | 
|||
| 
	
	
		
			
			 
The other day I flew an ILS into KCNO. The G1000 did not decode the Morse  
		
	
		
		
		
		
		
	
		 
		
	
	
	code and the 3 letter identifier did not appear. I was not in IMC and I did not manually listen to the Morse code. The ATIS did not indicate a problem. The localizer and glide slope appeared good. My question. What are some of the reasons to explain why I did not receive a 3 letter code? In actual IMC, if I did not receive a 3 letter code, I would have manually checked the Morse code. I know some probably always manually check the Morse code. Any comments are appreciated.  | 
| Thread Tools | |
| Display Modes | |
		
  | 
	
		
  | 
			 
			Similar Threads
		 | 
	||||
| Thread | Thread Starter | Forum | Replies | Last Post | 
| New Identifier For Pierce County Airport (Thun Field) | RL Anderson | Piloting | 6 | January 20th 07 05:56 PM | 
| 480 vs 430/G1000 | Robert M. Gary | Piloting | 28 | October 9th 06 11:34 PM | 
| "K" in VOR identifier | Jack Cunniff | Instrument Flight Rules | 3 | February 2nd 04 05:54 PM | 
| "K" in VOR identifier | Jack Cunniff | Piloting | 3 | February 2nd 04 05:54 PM | 
| Airport Identifier Logic | Jay Honeck | Piloting | 17 | August 14th 03 07:58 PM |