Alas! I finally understand the issue. Thank you for bringing this to my attention and for being persistent until my old brain finally got to understand the problem. I will sort this out in the next release. Regards, Robert On Tue, Sep 10, 2013 at 12:57 PM, Noel Romey <nromey@xxxxxxxxx> wrote: > Robert, > The cvrt has the complete data and is completely correct. What I hear > Michelle say is just the first four digits and zulu. So for instance, when > it is 041456z I hear Michelle say 0414 zulu only. I am not sure if this is > my system or if anyone else can confirm but I can tell you that using the > latest iyp version Michelle's reading only four digits of the time code. > Does that make things more clear or am I confusing the issue again smile. > > Sorry to make things difficult for you. > > Noel. > > On Sep 10, 2013, at 2:53 PM, Robert Cezar <robert@xxxxxxxxxxxxxxx> wrote: > > Hello Noel, > > REGARDING: What you're doing wrong with your code is the first two digits > of the time code (the metar) are the day of the mnth, for stance 10 for > 10 septamber. > > Well, not to be argumentative, but what IYP delivers is 100% correct. I > gave you this like earlier in this thread: > > http://weather.cod.edu/notes/metar.html > > As I stated early on, it is a very good read. > > In there is states: > > 041656Z-Time and Date > The 04 represents the day of the month > The 1656 represents the time at which the observation went out > The Z represents that the time is in ZULU or UTC (Universal Time Code) > > For the ultimate guide to METAR and observations, please refer to the > Federal Meteorological Handbook No. 1 from the National Weather Service > located here: > > http://www.ofcm.gov/fmh-1/fmh1.htm > > I hope this helps. > > Regards, > Robert > > > > > > On Tue, Sep 10, 2013 at 5:24 AM, Noel Romey <nromey@xxxxxxxxx> wrote: > >> Robert, >> >> I found the problem. >> >> The metar I got matches with yours. What you're doing wrong with your >> code is the first two digits of the time code (the metar) are the day >> of the mnth, for stance 10 for 10 septamber. Then the next four are >> the utc, then you have it correct. So now, I get the following metar. >> >> KPHX 101151Z 00000KT 10SM SCT080 BKN095 BKN220 24/19 A2978 RMK AO2 >> SLP069 70050 T02390194 10250 20233 55000 >> >> >> which translates to >> KPHX (PHOENIX/SKY HRBR, AZ, US) observed 1151 UTC 10 September 2013 >> Temperature: 23.9°C (75°F) >> Dewpoint: 19.4°C (67°F) [RH = 76%] >> Pressure (altimeter): 29.78 inches Hg (1008.5 mb) >> [Sea-level pressure: 1006.9 mb] >> Winds: calm >> Visibility: 10 or more miles (16+ km) >> Ceiling: 9500 feet AGL >> Clouds: scattered clouds at 8000 feet AGL >> broken clouds at 9500 feet AGL >> broken clouds at 22000 feet AGL >> Weather: no significant weather observed at this time >> >> >> -------------------------------------------------------------------------------- >> >> >> >> This is why iyp keeps saying 1011 utc and why I got 0203 utc on the >> second of September. >> >> Noel >> >> >> On 9/10/13, Robert Cezar <robert@xxxxxxxxxxxxxxx> wrote: >> > Hi, >> > >> > Ask for the METAR weather from IYP and view the METAR data printed in >> the >> > Cockpit Voice Recorder Transcript (CVRT) file in the IYPLogs folder. >> > >> > (For details on CVRT files, refer to PAGE 176 of the IYP Users' manual) >> > >> > The METAR data will look like this: >> > >> > KPHX 101051Z 00000KT 10SM SCT080 BKN095 BKN220 24/19 A2978 RMK AO2 >> SLP066 >> > T02440189 >> > >> > Then go here: >> > >> > http://aviationweather.gov/adds/metars/ >> > >> > and enter the same ICAO. >> > >> > Tell me if there's any difference. >> > >> > Thanks. >> > >> > >> > >> > On Tue, Sep 10, 2013 at 4:36 AM, Robert Cezar >> > <robert@xxxxxxxxxxxxxxx>wrote: >> > >> >> Please ask for the weather at KPHX right now. >> >> >> >> Thank you >> >> >> >> >> >> On Tue, Sep 10, 2013 at 4:06 AM, Noel Romey <nromey@xxxxxxxxx> wrote: >> >> >> >>> Well, I originally was talking about get weather. Then Mitchell asked >> >>> about problems he was having with get local weather. I still continue >> >>> having problems with get weather returning correct metar observations >> >>> but incorrect Zulu times. Sorry to confuse, two topics got rolled up >> >>> in to this thing. >> >>> >> >>> Noel >> >>> >> >>> >> >>> On 9/9/13, Robert Cezar <robert@xxxxxxxxxxxxxxx> wrote: >> >>> > Now I am completely and utterly confused. >> >>> > >> >>> > What are we talking about? >> >>> > >> >>> > 1. "Get the weather for Charlie Yankee Victor Romeo" >> >>> > >> >>> > or, >> >>> > >> >>> > 2. "Get local weather" >> >>> > >> >>> > Number one selects the current active weather for the declared ICAO. >> >>> > Number two selects the weather selected in the simulator. >> >>> > >> >>> > Please select 1 or 2. >> >>> > >> >>> > Regards, >> >>> > Robert >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > On Mon, Sep 9, 2013 at 5:05 PM, Noel Romey <nromey@xxxxxxxxx> >> wrote: >> >>> > >> >>> >> My original concern was with get weather. >> >>> >> >> >>> >> >> >>> >> >> >>> >> On Sep 9, 2013, at 3:49 PM, hadi <hadirezaei@xxxxxxx> wrote: >> >>> >> >> >>> >> Robert, they are talking about >> >>> >> "get local weather" >> >>> >> >> >>> >> On 9/10/2013 12:00 AM, Robert Cezar wrote: >> >>> >> >> >>> >> Quite the opposite. Perhaps I didn't explain it properly. >> >>> >> >> >>> >> RESTATED: >> >>> >> If the FSX application is in the foreground, and the BVI mode is >> >>> active, >> >>> >> then the ATC windows is forced open. Is that any clearer? >> >>> >> >> >>> >> Robert >> >>> >> >> >>> >> >> >>> >> >> >>> >> On Mon, Sep 9, 2013 at 12:09 PM, Mitchel Snel >> >>> >> <brailletijger@xxxxxxxxx>wrote: >> >>> >> >> >>> >>> dear Robert, >> >>> >>> does this mean that when iyp is in the bvi mode it will not work? >> >>> >>> greetings, Mitchel >> >>> >>> >> >>> >>> 2013/9/9, Robert Cezar <robert@xxxxxxxxxxxxxxx>: >> >>> >>> > Hello, >> >>> >>> > >> >>> >>> > When running in the BVI mode, the ATC window is forced open at >> all >> >>> >>> times. >> >>> >>> > If it is inadvertently closed, the IYP application forces it to >> >>> >>> > the >> >>> >>> > open >> >>> >>> > state immediately. However, the simulator application must be in >> >>> >>> > the >> >>> >>> > foreground. >> >>> >>> > >> >>> >>> > Robert >> >>> >>> > >> >>> >>> > >> >>> >>> > >> >>> >>> > On Mon, Sep 9, 2013 at 10:05 AM, hadi <hadirezaei@xxxxxxx> >> wrote: >> >>> >>> > >> >>> >>> >> Same thing happening to me as well~ doesn't work >> >>> >>> >> >> >>> >>> >> >> >>> >>> >> On 9/9/2013 9:11 PM, Noel Romey wrote: >> >>> >>> >> >> >>> >>> >>> jMitchell, >> >>> >>> >>> >> >>> >>> >>> This has happened to me. Seems as if it has some odd thing >> >>> >>> >>> happen >> >>> >>> >>> with the key presses on atc. The ATC window has to be open >> when >> >>> the >> >>> >>> >>> keypresses happen and sometimes, those keypresses don't seem >> to >> >>> >>> >>> work. >> >>> >>> >>> >> >>> >>> >>> Noel >> >>> >>> >>> >> >>> >>> >>> >> >>> >>> >>> On 9/9/13, Mitchel Snel <brailletijger@xxxxxxxxx> wrote: >> >>> >>> >>> >> >>> >>> >>>> sorry problem with my braille display! >> >>> >>> >>>> if I ask michell for the weather with the get local weather >> >>> command >> >>> >>> >>>> I >> >>> >>> >>>> get a announcement when there is no local weather but >> sometimes >> >>> >>> >>>> I >> >>> >>> >>>> get >> >>> >>> >>>> no responds. >> >>> >>> >>>> I assume that there is local weather then but I do not get >> the >> >>> >>> >>>> local >> >>> >>> >>>> weather? >> >>> >>> >>>> greetings, Mitchel >> >>> >>> >>>> >> >>> >>> >>>> 2013/9/9, Mitchel Snel <brailletijger@xxxxxxxxx>: >> >>> >>> >>>> >> >>> >>> >>>>> dear Robert, >> >>> >>> >>>>> sorry that I move into this topic but if I ask michel >> >>> >>> >>>>> >> >>> >>> >>>>> 2013/9/9, Robert Cezar <robert@xxxxxxxxxxxxxxx>: >> >>> >>> >>>>> >> >>> >>> >>>>>> The METAR data comes from the United States NOAA service >> >>> located >> >>> >>> >>>>>> here: >> >>> >>> >>>>>> >> >>> >>> >>>>>> http://aviationweather.gov/ >> >>> >>> >>>>>> >> >>> >>> >>>>>> I would suggest that you direct your questions to them >> >>> directly. >> >>> >>> >>>>>> >> >>> >>> >>>>>> Please let me know what they say. >> >>> >>> >>>>>> >> >>> >>> >>>>>> Thanks, >> >>> >>> >>>>>> Robert >> >>> >>> >>>>>> >> >>> >>> >>>>>> >> >>> >>> >>>>>> >> >>> >>> >>>>>> >> >>> >>> >>>>>> >> >>> >>> >>>>>> >> >>> >>> >>>>>> On Mon, Sep 9, 2013 at 9:06 AM, Noel Romey < >> nromey@xxxxxxxxx> >> >>> >>> wrote: >> >>> >>> >>>>>> >> >>> >>> >>>>>> Robert, >> >>> >>> >>>>>>> >> >>> >>> >>>>>>> I don't have a problem with the metar obversations, just >> the >> >>> >>> >>>>>>> ones >> >>> >>> >>>>>>> announced by iyp as relates to time. I pulled two >> reports, >> >>> one >> >>> >>> for >> >>> >>> >>>>>>> kphx (Phoenix Sky Harbor) and one for KLIT (Little Rock). >> I >> >>> >>> pulled >> >>> >>> >>>>>>> klit twoce actually. Both reports from kphx and klit were >> >>> >>> >>>>>>> correct >> >>> >>> >>>>>>> as >> >>> >>> >>>>>>> far as conditions, but the time reported was 0914. a 31 C >> >>> >>> >>>>>>> temperature >> >>> >>> >>>>>>> at 3 A>M. in Little Rock is probably not completely >> correct. >> >>> I >> >>> >>> >>>>>>> pulled >> >>> >>> >>>>>>> KLIT a second time with a flight loaded to Little Rock. >> >>> >>> >>>>>>> That >> >>> >>> time, >> >>> >>> >>>>>>> I >> >>> >>> >>>>>>> got a 0915 Zulu time, and a temperature of 32. >> >>> >>> >>>>>>> >> >>> >>> >>>>>>> Is there a problem with the scrape of the new metar data? >> >>> >>> >>>>>>> >> >>> >>> >>>>>>> Noel >> >>> >>> >>>>>>> >> >>> >>> >>>>>>> >> >>> >>> >>>>>>> On 9/9/13, Robert Cezar <robert@xxxxxxxxxxxxxxx> wrote: >> >>> >>> >>>>>>> >> >>> >>> >>>>>>>> Hi, >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> REGARDING: METAR updates >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> The METAR reports are typically updated at the end of >> each >> >>> >>> >>>>>>>> hour. >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> Here's a good link that describes METAR in detail: >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> http://weather.cod.edu/notes/**metar.html< >> >>> >>> http://weather.cod.edu/notes/metar.html> >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> Regards, >> >>> >>> >>>>>>>> Robert >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> On Mon, Sep 9, 2013 at 6:32 AM, Noel Romey >> >>> >>> >>>>>>>> <nromey@xxxxxxxxx >> >>> > >> >>> >>> >>>>>>>> wrote: >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> I'm making out. Have found a few cosmetic if you will >> bugs >> >>> >>> which I >> >>> >>> >>>>>>>>> will >> >>> >>> >>>>>>>>> compile and send privately. When I ask to check weather >> >>> >>> >>>>>>>>> for >> >>> a >> >>> >>> >>>>>>>>> location >> >>> >>> >>>>>>>>> the >> >>> >>> >>>>>>>>> conditions seem to be ok but Zulu Time doesn't update >> >>> >>> >>>>>>>>> much. >> >>> >>> >>>>>>>>> Does >> >>> >>> >>>>>>>>> the >> >>> >>> >>>>>>>>> new >> >>> >>> >>>>>>>>> service for metar not update often or is there some >> other >> >>> >>> problem? >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> Thanks >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> Ner >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> On Sep 8, 2013, at 4:08 PM, Robert Cezar < >> >>> >>> robert@xxxxxxxxxxxxxxx> >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>> wrote: >> >>> >>> >>>>>>> >> >>> >>> >>>>>>>> Hi, >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> How are you making out? >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> Robert >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> On Wed, Sep 4, 2013 at 8:04 AM, Noel Romey < >> >>> nromey@xxxxxxxxx> >> >>> >>> >>>>>>>>> wrote: >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> Hi guys, >> >>> >>> >>>>>>>>>> >> >>> >>> >>>>>>>>>> I was flying this morning from cyyc o cyxj. About 180 >> >>> miles >> >>> >>> from >> >>> >>> >>>>>>>>>> the >> >>> >>> >>>>>>>>>> airport, I sneezed into the microphone. It was not >> muted >> >>> >>> >>>>>>>>>> unfortunately. MS Speech Recognition took my sneeze >> as a >> >>> >>> >>>>>>>>>> keypress. >> >>> >>> >>>>>>>>>> two things happened in succession. First, I should >> say, >> >>> >>> >>>>>>>>>> these >> >>> >>> >>>>>>>>>> keypresses were on the FSX side, not the IYP Michelle >> >>> >>> >>>>>>>>>> side >> >>> of >> >>> >>> >>>>>>>>>> things. >> >>> >>> >>>>>>>>>> First, the autopilot got turned off and second, my >> engine >> >>> >>> mixture >> >>> >>> >>>>>>>>>> was >> >>> >>> >>>>>>>>>> set to lean. I dropped from 1000 to nothing in about >> 10 >> >>> >>> seconds. >> >>> >>> >>>>>>>>>> Didn't know what happened because I didn't know what I >> >>> >>> >>>>>>>>>> pressed, >> >>> >>> >>>>>>>>>> so >> >>> >>> >>>>>>>>>> I >> >>> >>> >>>>>>>>>> thought fist to set engine mixture to rich, well I said >> >>> lean, >> >>> >>> so >> >>> >>> >>>>>>>>>> I >> >>> >>> >>>>>>>>>> ultimately pulled back up to about 4000 feet, then fell >> >>> back. >> >>> >>> In >> >>> >>> >>>>>>>>>> essence, FSX was confused. Finally got things dialed >> >>> >>> >>>>>>>>>> back >> >>> >>> >>>>>>>>>> in, >> >>> >>> >>>>>>>>>> and >> >>> >>> >>>>>>>>>> got >> >>> >>> >>>>>>>>>> up to 10300 feet and climbing, aTC yelling at me that I >> >>> >>> >>>>>>>>>> was >> >>> >>> above >> >>> >>> >>>>>>>>>> my >> >>> >>> >>>>>>>>>> altitude. That's when I found that autopilot got >> turned >> >>> off. >> >>> >>> I >> >>> >>> >>>>>>>>>> would >> >>> >>> >>>>>>>>>> have started over because in real life, I would have >> been >> >>> >>> >>>>>>>>>> exploded >> >>> >>> >>>>>>>>>> into bits on the middle of frontier Canada, but I flew >> >>> >>> >>>>>>>>>> the >> >>> >>> flight >> >>> >>> >>>>>>>>>> last >> >>> >>> >>>>>>>>>> night and on approach, lost all FSX sound (nothing I >> >>> >>> >>>>>>>>>> could >> >>> >>> >>>>>>>>>> do >> >>> >>> to >> >>> >>> >>>>>>>>>> get >> >>> >>> >>>>>>>>>> it back either), so II just continued flying. I've got >> >>> >>> >>>>>>>>>> FSX >> >>> >>> >>>>>>>>>> set >> >>> >>> >>>>>>>>>> to >> >>> >>> >>>>>>>>>> not >> >>> >>> >>>>>>>>>> allow for crashes for some reason apparently under >> >>> >>> >>>>>>>>>> realism >> >>> (I >> >>> >>> had >> >>> >>> >>>>>>>>>> not >> >>> >>> >>>>>>>>>> idea that could be set). Luckily for me, I'm save in >> >>> >>> >>>>>>>>>> Fort >> >>> >>> >>>>>>>>>> St. >> >>> >>> >>>>>>>>>> John. >> >>> >>> >>>>>>>>>> >> >>> >>> >>>>>>>>>> Another note, upon landing, I got to 100 feet and the >> >>> >>> >>>>>>>>>> wind >> >>> >>> >>>>>>>>>> blew >> >>> >>> >>>>>>>>>> me >> >>> >>> >>>>>>>>>> up >> >>> >>> >>>>>>>>>> so I was a few feet from the ground but not landed and >> I >> >>> >>> >>>>>>>>>> didn't >> >>> >>> >>>>>>>>>> hear >> >>> >>> >>>>>>>>>> a >> >>> >>> >>>>>>>>>> bump or crash sound. So I pulled up (execute go around >> >>> >>> >>>>>>>>>> didn't >> >>> >>> >>>>>>>>>> work >> >>> >>> >>>>>>>>>> for some reason) flew a while and then prepared to land >> >>> >>> >>>>>>>>>> at >> >>> >>> >>>>>>>>>> the >> >>> >>> >>>>>>>>>> runway. >> >>> >>> >>>>>>>>>> Autopilot was on again again so I turned it off, did >> >>> >>> >>>>>>>>>> approach >> >>> >>> >>>>>>>>>> checklist again, and was able to land. I think that >> >>> >>> >>>>>>>>>> crosswinds >> >>> >>> >>>>>>>>>> caused >> >>> >>> >>>>>>>>>> problems for me, so when I came back the second time, >> >>> >>> >>>>>>>>>> they >> >>> >>> >>>>>>>>>> weren't >> >>> >>> >>>>>>>>>> as >> >>> >>> >>>>>>>>>> significant so Michelle was able to help. >> >>> >>> >>>>>>>>>> >> >>> >>> >>>>>>>>>> This is going to be a challenging trip. >> >>> >>> >>>>>>>>>> >> >>> >>> >>>>>>>>>> Noel >> >>> >>> >>>>>>>>>> Blind and Visually impaired Pilots mailinglist >> >>> >>> >>>>>>>>>> //www.freelists.org/list/**bvipilots< >> >>> >>> //www.freelists.org/list/bvipilots> >> >>> >>> >>>>>>>>>> To post a message to the list, send a message to >> >>> >>> >>>>>>>>>> bvipilots@xxxxxxxxxxxxx >> >>> >>> >>>>>>>>>> To unsubscribe, send a message to >> >>> >>> >>>>>>>>>> bvipilots-request@freelists.**org< >> >>> >>> bvipilots-request@xxxxxxxxxxxxx>and >> >>> >>> >>>>>>>>>> put the word unsubscribe in the >> >>> >>> >>>>>>>>>> subject of your message. >> >>> >>> >>>>>>>>>> For other options such as digest, send a message to >> >>> >>> >>>>>>>>>> bvipilots-request@freelists.**org< >> >>> >>> bvipilots-request@xxxxxxxxxxxxx>and >> >>> >>> >>>>>>>>>> put the word help in the >> >>> >>> >>>>>>>>>> subject >> >>> >>> >>>>>>>>>> >> >>> >>> >>>>>>>>> of >> >>> >>> >>>>>>> >> >>> >>> >>>>>>>> your message. >> >>> >>> >>>>>>>>>> >> >>> >>> >>>>>>>>>> >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> -- >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> AOPA Member No: 06936977 >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>>> >> >>> >>> >>>>>>>> -- >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> AOPA Member No: 06936977 >> >>> >>> >>>>>>>> >> >>> >>> >>>>>>>> Blind and Visually impaired Pilots mailinglist >> >>> >>> >>>>>>> //www.freelists.org/list/**bvipilots< >> >>> >>> //www.freelists.org/list/bvipilots> >> >>> >>> >>>>>>> To post a message to the list, send a message to >> >>> >>> >>>>>>> bvipilots@xxxxxxxxxxxxx >> >>> >>> >>>>>>> To unsubscribe, send a message to >> >>> >>> >>>>>>> bvipilots-request@freelists.**org >> >>> >>> >>>>>>> <bvipilots-request@xxxxxxxxxxxxx>and put the word >> >>> unsubscribe in >> >>> >>> the >> >>> >>> >>>>>>> subject of your message. >> >>> >>> >>>>>>> For other options such as digest, send a message to >> >>> >>> >>>>>>> bvipilots-request@freelists.**org >> >>> >>> >>>>>>> <bvipilots-request@xxxxxxxxxxxxx>and put the word help in >> >>> >>> >>>>>>> the >> >>> >>> subject >> >>> >>> >>>>>>> of >> >>> >>> >>>>>>> your message. >> >>> >>> >>>>>>> >> >>> >>> >>>>>>> >> >>> >>> >>>>>> >> >>> >>> >>>>>> -- >> >>> >>> >>>>>> >> >>> >>> >>>>>> >> >>> >>> >>>>>> AOPA Member No: 06936977 >> >>> >>> >>>>>> >> >>> >>> >>>>>> Blind and Visually impaired Pilots mailinglist >> >>> >>> >>>> //www.freelists.org/list/**bvipilots< >> >>> >>> //www.freelists.org/list/bvipilots> >> >>> >>> >>>> To post a message to the list, send a message to >> >>> >>> >>>> bvipilots@xxxxxxxxxxxxx >> >>> >>> >>>> To unsubscribe, send a message to >> >>> >>> >>>> bvipilots-request@freelists.**org >> >>> >>> <bvipilots-request@xxxxxxxxxxxxx> >> >>> >>> and >> >>> >>> >>>> put the word unsubscribe in the subject >> >>> >>> >>>> of your message. >> >>> >>> >>>> For other options such as digest, send a message to >> >>> >>> >>>> bvipilots-request@freelists.**org >> >>> >>> <bvipilots-request@xxxxxxxxxxxxx> >> >>> >>> and >> >>> >>> >>>> put the word help in the subject of your >> >>> >>> >>>> message. >> >>> >>> >>>> >> >>> >>> >>>> Blind and Visually impaired Pilots mailinglist >> >>> >>> >>> //www.freelists.org/list/**bvipilots< >> >>> >>> //www.freelists.org/list/bvipilots> >> >>> >>> >>> To post a message to the list, send a message to >> >>> >>> >>> bvipilots@xxxxxxxxxxxxx >> >>> >>> >>> To unsubscribe, send a message to >> >>> >>> >>> bvipilots-request@freelists.**org < >> >>> bvipilots-request@xxxxxxxxxxxxx> >> >>> >>> and >> >>> >>> >>> put the word unsubscribe in the subject of your message. >> >>> >>> >>> For other options such as digest, send a message to >> >>> >>> >>> bvipilots-request@freelists.**org < >> >>> bvipilots-request@xxxxxxxxxxxxx> >> >>> >>> and >> >>> >>> >>> put the word help in the subject of your message. >> >>> >>> >>> >> >>> >>> >> >> >>> >>> >> Blind and Visually impaired Pilots mailinglist >> >>> >>> >> //www.freelists.org/list/**bvipilots< >> >>> >>> //www.freelists.org/list/bvipilots> >> >>> >>> >> To post a message to the list, send a message to >> >>> >>> >> bvipilots@xxxxxxxxxxxxx >> >>> >>> >> To unsubscribe, send a message to >> >>> >>> >> bvipilots-request@freelists.**org < >> >>> bvipilots-request@xxxxxxxxxxxxx> >> >>> >>> and >> >>> >>> >> put the word unsubscribe in the subject of your message. >> >>> >>> >> For other options such as digest, send a message to >> >>> >>> >> bvipilots-request@freelists.**org < >> >>> bvipilots-request@xxxxxxxxxxxxx> >> >>> >>> and >> >>> >>> >> put the word help in the subject of your message. >> >>> >>> >> >> >>> >>> > >> >>> >>> > >> >>> >>> > >> >>> >>> > -- >> >>> >>> > >> >>> >>> > >> >>> >>> > AOPA Member No: 06936977 >> >>> >>> > >> >>> >>> Blind and Visually impaired Pilots mailinglist >> >>> >>> //www.freelists.org/list/bvipilots >> >>> >>> To post a message to the list, send a message to >> >>> >>> bvipilots@xxxxxxxxxxxxx >> >>> >>> To unsubscribe, send a message to >> >>> >>> bvipilots-request@xxxxxxxxxxxxx and put the word unsubscribe in >> the >> >>> >>> subject of your message. >> >>> >>> For other options such as digest, send a message to >> >>> >>> bvipilots-request@xxxxxxxxxxxxx and put the word help in the >> subject >> >>> of >> >>> >>> your message. >> >>> >>> >> >>> >> >> >>> >> >> >>> >> >> >>> >> -- >> >>> >> >> >>> >> >> >>> >> AOPA Member No: 06936977 >> >>> >> >> >>> >> >> >>> >> >> >>> > >> >>> > >> >>> > -- >> >>> > >> >>> > >> >>> > AOPA Member No: 06936977 >> >>> > >> >>> Blind and Visually impaired Pilots mailinglist >> >>> //www.freelists.org/list/bvipilots >> >>> To post a message to the list, send a message to >> >>> bvipilots@xxxxxxxxxxxxx >> >>> To unsubscribe, send a message to >> >>> bvipilots-request@xxxxxxxxxxxxx and put the word unsubscribe in the >> >>> subject of your message. >> >>> For other options such as digest, send a message to >> >>> bvipilots-request@xxxxxxxxxxxxx and put the word help in the subject >> of >> >>> your message. >> >>> >> >> >> >> >> >> >> >> -- >> >> >> >> >> >> AOPA Member No: 06936977 >> >> >> >> >> > >> > >> > -- >> > >> > >> > AOPA Member No: 06936977 >> > >> Blind and Visually impaired Pilots mailinglist >> //www.freelists.org/list/bvipilots >> To post a message to the list, send a message to >> bvipilots@xxxxxxxxxxxxx >> To unsubscribe, send a message to >> bvipilots-request@xxxxxxxxxxxxx and put the word unsubscribe in the >> subject of your message. >> For other options such as digest, send a message to >> bvipilots-request@xxxxxxxxxxxxx and put the word help in the subject of >> your message. >> > > > > -- > > > AOPA Member No: 06936977 > > -- AOPA Member No: 06936977