{"efta_number": "EFTA01738251", "page_count": 6, "url": "https://epstein-data.com/EFTA01738251", "pdf_url": "https://epstein-data.com/pdf/EFTA01738251.pdf", "pages": [{"efta_number": "EFTA01738251", "page_number": 0, "text_content": "From: \nRichard Kahn \nSubject Fwd: ZDC Future Tee Sight Visit \nSent \nMonday, May 23, 2016 8:43:02 PM \nTo: \n\"Jeffrey E.\" leevacationegmail.com> \nIMG 2930.JPG \nIMG 2935.JPG \nIMG 2932.JPG \nwe should have answer tomorrow on whether or not sandia to main house will work \nnote - \ncurrently is saying height of main house pole may need to be 30' vs 20' it currently is \nwhich may make it visible from the back parking area \nRichard Kahn \nHBRK Associates Inc \nBegin forwarded message: \nFrom: \nSubject: ZDC Future Tec Sight Visit \nDate: May 21. 2016 at 12 01 50 PM EDT \nTo: Richard Kahn O> \nRich \nUpdate from Site Visit \nLine of Sight from Sandia Crest to MH was determined by \nthe conditions where to hazy to determine any other way \nflashing a signal mirror, \nAs already stated the Path is very close to the top right of the mountain \nFuture Tech recommendation at this time is to place the dish on Sandia tower to 72 \nThe 3rd photo of climber Is the approx location of new Dish. The Main house dish \nis to be set at approx 30 ft. \nThis will require either a new pole or extending existing pole at Main house . Noting MH \npole will extend past the apex of the mechanical building roof and will be visible \nfrom the back parking area. This will need to brought to the Jeffrey's attention \nWe should receive Confirmation of which path is most viable by Tuesday next week. \nI have requested that Future Tech contact Sierra Nevada, regarding proposed build out, \njust incase there is an engineering issue with dish size and height on existing tower. \nEFTA_R1_00025477 \nEFTA01738251\n", "char_count": 1571}, {"efta_number": "EFTA01738251", "page_number": 1, "text_content": "Lastly I have received notice from Centurylink indicating present service provision will \nexpire at the end of the month \nI will forward notice separately \nRegards \nEFTA_R1_00025478 \nEFTA01738252\n", "char_count": 196}, {"efta_number": "EFTA01738251", "page_number": 2, "text_content": "N \nN\nEFTA_R 1_00025479 \nEFTA01738253\n", "char_count": 37}, {"efta_number": "EFTA01738251", "page_number": 3, "text_content": "N \nN\nEFTA_R 1_00025480 \nEFTA01738254\n", "char_count": 37}, {"efta_number": "EFTA01738251", "page_number": 4, "text_content": "N \nEFTA_R1_00025481 \nEFTA01738255\n", "char_count": 34}, {"efta_number": "EFTA01738251", "page_number": 5, "text_content": "Sent from my iPhone \nEFTA_R1_00025482 \nEFTA01738256\n", "char_count": 52}]}