TAGBOARD MISSIONS

Document Type: 
Collection: 
Document Number (FOIA) /ESDN (CREST): 
CIA-RDP79B01709A000100060007-9
Release Decision: 
RIPPUB
Original Classification: 
T
Document Page Count: 
5
Document Creation Date: 
December 14, 2016
Document Release Date: 
May 9, 2003
Sequence Number: 
7
Case Number: 
Publication Date: 
March 20, 1970
Content Type: 
MF
File: 
AttachmentSize
PDF icon CIA-RDP79B01709A000100060007-9.pdf201.42 KB
Body: 
25X1 L. ' Approved For Rete a 2003/05 C X B01709AO 00060007-9 NATIONAL RECONNAISSANCE OFFICE WASHINGTON, D.C. March 20, 1970 MEMORANDUM FOR Assistant to the President for National Security Affairs Attorney General. Deputy Secretary of Defense Under Secretary of State (Political Affairs) Director of Central Intelligence Executive Secretary, 40 Committee SUBJECT: TAGBOARD Missions Following. is a brief summary of the November 10, 1969 operational mission and the February 20, 1970 test mission. A summary of all flights to date is attached. TAGBOARD flew its first limited operational mission over South China on November 10, 1969. Launch and early flight were successful as the drone obtained the programmed altitude of 84,000 feet and a cruise mach of 3.27. During the terminal phase of the flight the drone was not acquired (visually or electronically) and the payload was not recovered. NSA reported no SIGINT that could be correlated with the mission. The drone's position was fixed at only 50 miles off the Island of Hainan and 80 miles from the China mainland, just prior to the drone's telemetry being turned off on the inbound track well within range of coastal air defense radars. The drone's operating altitude, speed and small radar cross section (.2 sq meter frontal area with a 150 depression angle) give it a high probability of survival. Investigations and laboratory simulations now indicate that computational errors in the drone's inertial navigation system (INS) prevented the drone.from flying the programmed 25X1A MIA N-RO Apoomp Yd',re ?Jase 2003/05/28: CIA-RDP79BO1709A000100060007~~Tpo~ ~~_ IV SLURL-l COPY_ -Of--- 'Icy 1 J~X?4 J1 ~ WX'A_X_XN X_l_}l X-A k x x x Jk A nAl~nnr ? Approved For Release 2003/05/28 : CIA-RDP79BO1709A000100060007-9 TOP SECRET route. Self destruction probably occurred after fuel exhaus- Software changes have since been made and tested to correct the computational errors, and a "fail safe" feature has been incorporated in the INS that will provide positive control of -the drone's flight path. On February 20, 1970, TAGBOARD flew a completely success- ful test mission to validate the software and "fail safe" changes to the INS program, 25X1A~ tion upon descent at the pre-set altitude 25X1A~, The TAGBOARD system is now ready for another operational test mission. Drones are located at Beale AFB and are ready for flight. 1 Attachment Summary of Flights ILLEGIB. Approved For Release 2003/05/28 : CIA-RDP79BO1709A000100060007-9 25X1A TfD CF:r'nF:T ....D XXX X X X X X X X A X A A A A A n n .a n n n ............ - - 25X1A 25X1 SUMMARY OF TAGBOARD B-52 LAUNCHES November 6, 1967. Drone #507. PMR. (PACIFIC MISSILE RANGE) Launch and boost were 25X1A 25X1A Launch and boo successful. Free flight continued on course for feet less than normal). Flight terminated prema ure y after failure of the hydraulic system and subsequent loss of control. The hatch was not recovered. Approved For Release 2003/ ( 791301709A0 0 00060007-9 hatch was not recovered. successful. Drone attained a mach Cruise flight was not sustained due to low inlet recovery; deformed inlet cone primary suspect. Drone travelled 134 miles down range and the December 22 1967. Drone #509. PMR. January 1.9, 1968. Drone #508. PMR. Launch and.boost were successful. The drone travelled 550 miles down range, then the flight terminated prematurely when the drone began a pitch down and roll to the left. Telemetry was lost. Most probable cause of failure was electrical malfunction. The hatch was not recovered. April 30, 1968. Drone #511. PMR. - Launch and boost were successful. Following booster ejection, the drone was unable to sustain cruise and lost altitude and speed due to low thrust from the engine (in- let not started). Drone travelled 150 miles down range and was destroyed. Hatch-not recovered. June 16, 1968. Drone #512. PMR.? Successful test flight. I The hatch was air-recovered by JC-IJU alrcra . Approved For Release 2003/05/28 : CIA-RDP79BO1709A000100060007-9 25X1A CONTROL NO 1 ~~? Tnn /~ lrcar I.- / I/f I___CQPICI .XXa.~ XX+~nnnrv~nrnn vvv..vvvvvV V V V V V V S S S ................... 5/X1 A X. Approved For Re ea a 2003/0 B01709AOO 00060007-9 Ef O July 1, 1968. Drone #514. PMR. During pushover at the top of boost phase, the drone became laterally unstable due to insufficient-autopilot gains. At separation, the booster struck the drone, rupturing the drone's fuel tank. The hatch ejected upon command and was recovered from the water in good condition. August 28, 1968. Drone #516. PMR. Launch and boost were successful. However, the drone's engine remained at minimum power and cruise altitude was not maintained. The hatch ejected at an excessive speed on descent and was not recovered. December 15, 1968. Drone #515. PMR. t flijzht. , 25X1A This was the first mission to test the total system with the camera aboard. The hatch was air-recovered by JC-130. 25X1' NNNRRR 25X- February 11, 1969. Drone #518. PMR. Launch and boost successful. Apparent shift in autopilot control at excessive mach caused the drone to descend resulting in the inlet remaining only partially started with attendant loss in thrust. Severe--asoillations resulted. Drone believed to have structurally destroyed itself. Hatch was'not recovered. May 10, 1969. Drone #519. PMR. Successful test flight. July 10, 1969. Drone #520. PMR. Successful test flight. I 25X1A Hatch was air recovered by JC-130. 25X1A Hatch was air-recovered by JC-130. Approved For Release 2003/05/28 : CIA-RDP79BO1709A000100060007-9 CONTROL NO T enT /J Approved For Release 2003/05M ~t-~ P79B01709A00100060007-9 November 10, 1969. Drone #517. First operational mission. Launch and boost successful. Computational errors in the drone's Inertial Navigation System prevented drone from flying the programmed route. Self-destruct believed to have occurred upon descent at 0 feet. Hatch was 25X1A not recovered. February 20, 1970.. Drone-#521. PMR. 25X1"A Successful test flight. 1 ::1 Changes to INS program validated. Hatch was air-recovered by JC-130. 25X1 Approved For Release 2003/05/28 : CIA-RDP79BO1709A000100060007-9 CONTROL NO e%rnnr