Planet Labs 最新添加的 Flock (Flock 4x) 是另外 44 颗 SuperDove 卫星,这些卫星于 2022 年 1 月 13 日由 SpaceX Falcon 9 火箭成功发射。这 44 颗卫星将加入由大约 200 颗卫星组成的现有轨道上的 PlanetScope Dove 卫星星座,并将提供具有 8 个光谱带的 3 米高分辨率卫星图像。鸽群卫星是美国Planet公司研制的3U遥感立方体卫星星座,单颗卫星重约5kg,也被称为“鸽子”(Dove)。鸽群星座主要有两类轨道:空际空间站释放420km高、52度倾角轨道(ISS),以及运载火箭释放475km高、98度倾角太阳同步轨道(SSO)。Planet公司每3到6个月进行一次发射,维持200颗左右卫星可正常在轨运行。PlanetScope是由大约 130 颗卫星组成的星座,能够每天对地球的整个陆地表面进行成像(每日采集能力为 2 亿平方公里),PlanetScope 图像的分辨率约为 3 米。鸽群微纳卫星星座旨在每天更新地球的图像信息,监视地面的变化情况,利用宇宙空间收集到的信息为地面上生活的人们提供帮助。每颗卫星都配备了高倍率望远镜和相机可以实现对地3~5米分辨率的光学成像。鸽群卫星每天不断对地扫描,每当卫星过境地面站,便将数据下行传输给地面站。鸽群星座可以实现每天更新一次全球遥感影像,实现真正的对地观测。目前的应用领域包括物流、区域开发、农作物监测、城市化、自然资源管理、资产管理等。鸽群卫星的4颗前期试验卫星分别于2013年4月19日(Dove-2)、2013年4月21日(Dove-1)、2013年11月21日(Dove-3、Dove-4)发射;Flock-1星座于2014年1月9日首发,于2015年6月28日部署完成;Flock-2星座于2015年8月19日首发,于2017年7月14日部署完成;Flock-3星座于2017年2月15日首发,于2018年12月27日部署完成;Flock-4星座于2019年4月1日首发,Dove就像一个扫描仪一样,唯一使命就是为全球提供地球影像数据流。目前正在运营Dove和SkySat星座;而根据最新消息,Pelican(鹈鹕)将成为 Planet 的下一代卫星星座,将提供具有超高分辨率及快速重访能力,以补充和升级今天在轨的 21 个 SkySat。同时Planet是一家上市的遥感卫星公司。结构分系统:鸽群卫星外壳呈黑色,采用铝合金制成,质量很轻,外部是10cm×10cm×30cm的立方体结构,重约5kg。姿态与轨道控制系统:姿态控制方面配备一只星敏感器,一个GPS,一个粗太阳敏感器,一只磁力矩器和一台三自由度陀螺仪。Dove 3/4配备的星敏感器精度为0.01°,控制精度为1°。执行机构采用四面体构型的四个反作用飞轮和三轴磁力矩器。鸽群卫星不设置推进系统,卫星采用差分拖拽控制算法,通过控制卫星飞行姿态改变收到的大气阻力,使卫星最终能均匀的分布在轨道平面内。测控与数传:鸽群卫星采用UHF频段测控,上行频率约450MHz,发射功率100W,下行频率约401.3MHz,发射功率1W。卫星还可以利用S频段上行,发射功率100W,数据率可以达到250kbps,图像数据下传则采用X频段,数据率可以从12.5Mbps到超过100Mbps,发射功率2W。相应的,地面有UHF测控站和S/X双频测控站。一个轨内,通过X频段数传,地面可以接收4.2G数据,相当于170平方公里的图像。上传30kbit/s。光学系统:鸽群携带的有效载荷包括光学望远镜和高分辨率相机。当相机指向地球时,Dove可以进行地球表面成像; 当指向空间时,Dove可以提供碎片跟踪服务。2019年10月,Planet公司CEO Will Marshall称在未来计划将相机的光谱波段从3个逐渐提升到8个,得到的数据将在机器学习领域进行应用。鸽群卫星携带的光学望远镜孔径91mm,长20cm,大约2.5U。在3U立方体卫星中,留给其余设备的空间不大。此外,1.14m的焦距要求工业级CCD与望远镜镜头光圈之间的距离约为32cm,这意味着整套光学系统的长度略大于标准3U立方星的长度,因此卫星后部加了一个“tuna can”,并将CCD置于“tuna can”中。然而这又意味着卫星的后面1U中间需要留有一个狭窄的光路,光路上不能有设备穿过,因此卫星平台的后部电路板为1/4U的环形设计。空间十分狭小,但是任务目标决定了卫星需要一个完整的姿态控制系统,大量的计算和数据存储以及高带宽通信功能也都必须保留。为此,Planet借鉴了笔记本电脑、智能手机和平板电脑行业的经验,除了一些必要的大部件(飞轮)之外,卫星非常像是现代电子设备,印制电路板(PCB)的层数极多,表面贴装(SMT)的电子元件密度极高,几乎没有外部导线。大部分鸽群卫星通过同一次发射进入太空,在极短的时间内从火箭分离,大量卫星入轨后聚成一团。为了完成对地扫描观测任务,需要控制卫星分布在不同的相位,但是由于卫星太小,不具备推进系统,无法通过喷气等方式调整轨道。在较低的轨道高度上,比如500km以下,具有稀薄的大气,卫星在稀薄大气的拽拉下轨道会不断变化。鸽群都处在400至600km轨道高度,下图是单个卫星的三视图,可以看到不同的视向单个卫星的面积不一样,太阳帆板视向面积最大,而镜头视向面积最小。利用不同视向面积的不同,每颗卫星各自调整自己的姿态,使其受的大气阻力不同,从而调整轨道。这种控制方法叫做差分拖动控制方法。
2023年1月2日,Planet公司成功发射了36颗SuperDove卫星,并已经与所有卫星建立了联系,启动了自动化调试流程。 SuperDove卫星发射 鸽群星座(FLOCK)自Planet成立以来,已经成功发射了超500颗卫星,达到FLOCK 4y型号,目前在轨运行的数量超过200颗,是世界上最大的遥感卫星星座,具备对全球任意地点每天拍摄的能力。Planet发射记录 序号 | 星群名称 | 发射时间 | 颗数 | 序号 | 星群名称 | 发射时间 | 颗数 | 1 | FLOCK-1 | 2014年01月 | 28 | 14 | FLOCK-3m | 2017年10月 | 4 | 2 | FLOCK-1b | 2014年06月 | 28 | 15 | FLOCK-3p’ | 2018年01月 | 4 | 3 | FLCOK-1c | 2014年07月 | 11 | 16 | FLOCK-3r | 2018年11月 | 16 | 4 | FLCOK-1d | 2014年10月 | 26 | 17 | FLOCK-3s | 2018年12月 | 3 | 5 | FLOCK-1d’ | 2015年01月 | 2 | 18 | FLOCK-3k | 2018年12月 | 12 | 6 | FLOCK-1e | 2015年04月 | 14 | 19 | FLOCK-4a | 2019年04月 | 20 | 7 | FLOCK-1f | 2015年06月 | 8 | 20 | FLOCK-4p | 2019年11月 | 12 | 8 | FLOCK-2b | 2015年08月 | 14 | 21 | FLOCK-4e | 2020年07月 | 5 | 9 | FLOCK-2e | 2015年12月 | 12 | 22 | FLOCK-4v | 2020年09月 | 26 | 10 | FLOCK-2e’ | 2016年03月 | 20 | 23 | FLOCK-4e’ | 2020年10月 | 9 | 11 | FLOCK-2p | 2016年06月 | 12 | 24 | FLOCK-4s | 2021年01月 | 48 | 12 | FLOCK-3p | 2017年02月 | 88 | 25 | FLOCK-4x | 2022年01月 | 43 | 13 | FLOCK-2k | 2017年07月 | 4 | 26 | FLOCK-4y | 2023年01月 | 36 |
本次发射的36颗SuperDove卫星将补充现有在轨卫星星座,都配备了八个光谱波段,并提高了在轨容量,有助于快速向客户提供高质量的影像数据,进而辅助农业、林业等多行业应用及决策。 SpaceX 载有 48 架超级鸽子的 Transporter-1 任务升空PlanetScope Dove 卫星星座保持着单枚火箭一次发射卫星数量最多的世界纪录,每天将收集多达 200 万平方公里的图像。该卫星星座由 Planet Labs PBC 运营,由 120 多颗被称为 Doves 的纳米卫星组成,每颗卫星重量仅 5.8 公斤,为各种测绘应用提供 3 米多光谱图像分辨率,包括多种人道主义和环境应用,从监测森林砍伐和城市化到改善自然灾害救济和世界各地的农业产量。该星座的重访频率比任何现有的政府或商业卫星都要频繁。从太空来看,Planetscope 监控订阅服务为您提供真实数据,以支持持续的人工智能(AI) 算法,利用计算机视觉(CV) 管理系统做出及时、明智的决策。Dove-1 和 Dove-2 是用作技术演示任务的纳米卫星。该任务的目的是证明使用商用现成 (COTS) 组件来创建适合 3U 立方体卫星外形的低成本总线是可行的,并且可以在短期内以较低的成本运行。Dove-1 和 Dove-2 具有相同的传感器,其中包括一个孔径为 90 毫米的单一光学望远镜有效载荷和一个高分辨率相机。摄像机的方向决定了其用途,最低点摄像机用于表面成像,向上摄像机用于碎片跟踪。Dove-1和Dove-2的空间分辨率为4.4 m。鸽子一号原计划在近圆形轨道运行,目标高度为241公里×257公里,倾角为51.6°,但部署错误。Dove-2 的初始椭圆轨道运行高度约为 300 公里 x 575 公里,倾角为 64.9°。 | | |
|
| 带有分帧 VIS+NIR 滤光片的四波段帧成像仪 (DOVE-C) | | | | | | | | | | |
|
|
| | | |
|
|
| | | |
|
|
| | | |
|
|
| | | |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| | | |
|
| | |
|
| DOVE-R 24 km x 16 km(大约) SuperDOVE | | | |
|
| | |
|
| | |
|
| Dove-1 和 Dove-2 使用 ADCS(姿态确定和控制子系统),该子系统使用磁力计、陀螺仪和光电二极管来确定姿态和磁力,以与地球磁场轴对齐。EPS(电力子系统)为所有电子元件提供电力,并由八个锂离子电池提供存储。Dove-1和-2在美国旧金山接受运营管理。录制的图片被下载到美国肯塔基州。Dove-1 是 Cosmogia Inc.(美国加利福尼亚州桑尼维尔)的一项技术演示任务,其目标是:1)· 测试由非太空、COTS(商业现货)组件构建的低成本总线的基本功能· 表明受 3U CubeSat 外形尺寸限制的总线可以承载较小的有效负载· 展示在短时间内、以低成本设计、生产和运行卫星的能力。Cosmogia 是一家位于硅谷的 NASA 衍生公司,它正在使用 PhoneSat 航天器工程方法来生产 Dove-1 纳米卫星。Dove-1 符合 3U CubeSat 外形尺寸,尺寸为 10 cm x 10 cm x 30 cm,质量约为 5.8 kg。姿态由磁力计、陀螺仪和光电二极管感知。姿态由磁力矩器和反作用轮控制。B点控制器利用B场来降低卫星的角速率。因此,在这种控制模式下,Dove-1 表现为永久磁铁,保持锁定并与地球磁场轴对齐。- Dove-1 将在每个轨道上指向两次最低点。众所周知,任何一点的磁场排列大约为 1°。该总线通过相机、飞行计算机和磁力矩器的电源提供中央电源控制。电源调节电压并确保每个组件的稳定供电。电力存储由 8 节锂离子电池提供,满容量时可提供 20 Ah 的电量。电池将通过安装在车身上的 TASC(三角形先进太阳能电池)进行充电。C&DH由单板计算机控制。此外,还将有一个独立的看门狗板,可以在出现错误时重新启动飞行计算机。通信子系统由用于传输遥测数据的 VHF 无线电信标和用于双向通信并作为数据下载的主要无线电的 S 波段跳频扩频调制解调器组成。通电后,第一个任务事件是通过 VHF 信标传输遥测数据。信标将以 1200 波特率 AFSK 大约每 30 秒传输一次健康数据包(包括温度/电源/电流/RSSI/太阳矢量/加速度)(AX.25 协议,145.825 MHz)。该信标的发射功率高达 1 W,并将使用从卷尺上切割下来的四分之一波单极天线。S 波段无线电将在 2.4 GHz 半双工 ISM(工业、科学和医疗)波段运行,使用贴片天线,无线链路速率为 115 kbit/s。图 2:Dove 2 纳米卫星的照片(图片来源:Planet Labs Inc.)鸽子一号纳米卫星于2013年4月21日发射,作为OSC Antares-110(原金牛座二号)运载火箭首飞的第二有效载荷。发射地点是位于弗吉尼亚州瓦洛普斯岛的 MARS(大西洋中部区域太空港)。这次试飞的主要有效载荷是约 3800 公斤的天鹅座太空舱质量模拟器(轨道科学/美国宇航局),这是一个装备精良的有效载荷,用于收集 Antares 发射环境的数据。- 此外,还从两个分配器部署了四颗小卫星,这些分配器将与质量模拟器集成。这次发射是由 NASA COTS(商业轨道运输服务)计划资助的。2)轨道:近圆形轨道,目标高度约 241 公里 x 257 公里,倾角 = 51.6°。Antares 110 演示飞行的辅助有效载荷:3)· 2 PhoneSat-1,NASA/ARC(艾姆斯研究中心)的两个 1U CubeSat 的技术演示任务· NASA/ARC的PhoneSat-2、1U CubeSat技术演示任务· Dove-1,Cosmogia Inc.(美国加利福尼亚州桑尼维尔)的纳米卫星(3U CubeSat,~ 5.5 kg)技术演示任务。升空十分钟后,火箭将其有效载荷、模拟天鹅座航天器和几颗小型卫星释放到近地轨道,结束了一次成功的任务。这次发射对轨道公司和美国宇航局来说都是一次重大成功。对于 Orbital 来说,Antares 不仅代表了该公司有史以来建造的最大的火箭,而且也是对公司未来的一次重大赌注。Orbital 希望 Antares 不仅可以发射天鹅座货运任务,还可以发射其他卫星,特别是为美国政府发射的卫星,这些卫星之前是在 Delta II 上飞行的,Delta II 是一种中型火箭,将在未来几年退役。Antares 将为此类有效载荷提供“合适尺寸和合适价格”的发射服务,该公司称其为微妙的参考,即此类卫星现在必须使用更大、更昂贵的 EELV 级 Atlas V和德尔塔四号。- 对于美国宇航局来说,这次发射再次证明了其转向商业部门向国际空间站发射货物并最终向国际空间站发射宇航员的方法的正确性。4)安塔瑞斯完美的升空标志着美国宇航局和轨道科学公司之间的PPP(公共/私人合作伙伴关系)迈出了第一步,以重新启动在美国宇航局航天飞机轨道飞行器被迫退役后失去的国际空间站货物运输服务。图 3:Antares 火箭配置 – 由 Orbital Sciences Corp. 私人开发(图片来源:OSC)· 2013 年6 月26 日,前公司Cosmogia 宣布更名为Planet Labs Inc.,位于加利福尼亚州旧金山。该公司由前 NASA/ARC 科学家(Chris Boshuizen、Will Marshall、Robbie Schingler)创立,并包括领先的风险投资团队,包括 Draper Fisher Jurvetson (DFJ)、O'Reilly Alpha Tech Ventures (OATV)、Capricorn Investment Group、Founders Fund Angel、Data Collective、First Round Capital 和 Innovation Endeavors。5) 6) 7)6 月 26 日的新闻租约中随公司名称变更一起提供了以下公告:1) Planet Labs 宣布计划于 2014 年将一支由 28 颗名为 Doves 的纳米卫星组成的卫星群作为辅助有效载荷送入轨道。该公司的目标是运营“世界上最大的地球成像卫星群,对不断变化的星球进行成像并提供开放访问”到该信息。Planet Labs 希望定期、广泛地对地球进行成像,以便人们,包括农民、气象专业人士等,可以使用这些数据来采取行动。2) 该公司前两颗演示卫星 Dove-1(2013 年 4 月 21 日发射)和 Dove-2(2013 年 4 月 19 日发射)的精选图像可通过以下链接获取:http://planet- labs .com/Dove -2纳米卫星于 2013 年 4 月 19 日发射,作为主航天器 Bion-M1(具有俄罗斯和国际社会的生物和医疗有效载荷)的辅助有效载荷,由联盟号 2.1b 火箭发射。发射场是哈萨克斯坦的拜科努尔发射设施。8) 9)轨道:初始椭圆轨道,高度约为 300 公里 x 575 公里,倾角 = 64.9°。与运载火箭分离后,Bion-M1航天器将其轨道绕圆至575公里×575公里的高度。到达目标轨道后(发射后约 2 天),辅助有效载荷将从 Bion-M1 部署。· BEESAT-2,柏林工业大学的 1U 立方体卫星· BEESAT-3,柏林工业大学的 1U 立方体卫星·德累斯顿工业大学(TU(Technische Universität))或德国德累斯顿工业大学的SOMP (学生氧气测量项目)。· OSSI-1(开源卫星计划),由韩国艺术家宋浩俊发起的业余无线电立方体卫星。该卫星将携带一个 145 MHz 信标以及一个 435 MHz (UHF) 频段的数据通信收发器。它还将携带一个 44 W LED(发光二极管)阵列,向地球上的观察者闪烁莫尔斯电码信息。· Dove-2,Cosmogia Inc.(美国加利福尼亚州桑尼维尔)的纳米卫星(3U CubeSat,~ 5.8 kg)技术演示任务。· AIST-2是俄罗斯微型卫星项目,是一项技术示范项目,由萨马拉航空航天大学的学生、研究生和科学家与俄罗斯萨马拉的 TsSKB Progress 合作开发和设计。这颗质量为 39 公斤的微型卫星将执行为期 3 年的任务,专门测量地磁场并测试低频微加速度补偿方法。此外,该航天器还将研究自然和人造来源的高速机械粒子· 该项目采用了单独的设计,一个被称为“高风险”,另一个被称为“超高风险”。两颗卫星 Dove-1 和 Dove-2 开箱即用,可以立即使用(参考文献7)。将于 2014 年发射的鸽子卫星群将在仅 450 公里的相对较低轨道上运行。运行中的卫星将与Dove-1和-2类似,能够拍摄分辨率为3-5 m/像素的图像。由于部署时的轨道高度较低(241公里×257公里),鸽子一号纳米卫星于2013年4月27日重新进入大气层(为期6天的任务)。- 使用任务控制系统在 HMB(加利福尼亚州)和英国(Chilbolton 设施)进行自动遥测下行链路图 4:2013 年 4 月 24 日观察到的 Dove-1 样本图像(图片来源:Planet Labs)· 575 km x 575 km 的更高插入轨道将提供更长的任务寿命。- 使用任务控制系统在 HMB 和 UK (Chilbolton) 进行自动下行链路- 下载 MSU(莫尔黑德州立大学)天线盘(莫尔黑德,肯塔基州)的图片图 5:2013 年 5 月 1 日获取的日本静冈 Dove-2 样本图像(图片来源:Planet Labs)· Dove-2 结果(2013 年秋季正在进行):- 通过 2.4 GHz 无线电实现 30 kbit/s 有效负载上行链路- 从旧金山的任务总部部署和远程协调的 5 个地点Dove-1携带光学望远镜有效载荷(90 毫米孔径)和高分辨率相机。当天底指向时,仪器可用于地球表面成像;当指向上方时,Dove-1 可以提供碎片跟踪服务以支持 SSA(太空态势感知)。Dove-2使用与 Dove-1 相同的光学/相机系统,提供 4.4 m 的 GSD(地面采样距离)。PlanetScope(DOVA),PlanetScope是由大约 130 颗卫星组成的星座,能够每天对地球的整个陆地表面进行成像(每日采集能力为 2 亿平方公里),PlanetScope 图像的分辨率约为 3 米。 | 可获取红色、绿色、蓝色和近红外通道(4band)。它生产大约 25.0 x 11.5 平方公里的场景产品。SkySat最早可用的图像在2014 年 7 月至 2022 年 4 月 29 日 | | 在PS2基础上更新了传感器拜耳模式和通带滤光片,可获取红色、绿色、蓝色和近红外通道(4band)。它生产大约 25.0 x 23.0 平方公里的场景产品。最早可用的图像在 2019 年 3 月至 2022 年 4 月 22 日 | | 该仪器即在PSB.SD升级,除了获取红色、绿色、蓝色、近红外,以及新的红色边缘、绿色 I、沿海蓝色和黄色通道(8band)。它生产大约 32.5 x 19.6 平方公里的场景产品。最早的可用图像在 2020 年 3 月中旬到至今 |
| | | | | Reentry
2014-06-09. Was operational. | | | | Reentry
2014-05-24. Was operational. | | | | Reentry
2014-05-15. Was operational. | | | | Reentry
2014-06-18. Was operational. | | | | Reentry
2014-06-02. Was operational. | | | | Reentry
2014-06-15. Was operational. | | | | Reentry
2014-06-05. Was operational. | | | | Reentry
2014-05-25. Was operational. | | | | Reentry
2014-07-06. Was operational. | | | | Reentry
2014-06-14. Was operational. | | | | Reentry
2014-06-13. Was operational. | | | | Reentry
2014-10-26. Was operational. | | | | Reentry
2014-07-02. Was operational. | | | | Reentry
2014-06-20. Was operational. | | | | Reentry
2014-05-20. Was operational. | | | | Reentry
2014-06-20. Was operational. | | | | Reentry
2014-05-19. Was operational. | | | | Reentry
2014-10-29. Was operational. | | | | Reentry
2014-06-02. Was operational. | | | | Reentry
2015-10-09. Was operational. | | | | Reentry
2014-05-25. Was operational. | | | | Reentry
2014-06-04. Was operational. | | | | Reentry
2014-07-10. Was operational. | | | | Reentry
2014-06-16. Was operational. | | | | Reentry
2014-06-24. Was operational. | | | | Reentry
2014-06-10. Was operational. | | | | Reentry
2014-05-03. Was operational. | | | | Reentry
2014-06-03. Was operational. | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Was
operational? Retired, but not explained what it means (SmallSat 2017 paper) | | | | Reentry
2015-01-01. Was operational. | | | | Reentry
2015-03-14. Was operational. | | | | Returned
to Earth. Aboard Dragon SpX-5 | | | | Returned
to Earth. Aboard Dragon SpX-5 | | | | Reentry
2014-08-17. Was operational. | | | | Reentry
2015-10-16. Was operational. | | | | Reentry
2015-01-20. Was operational. | | | | Reentry
2015-03-05. Was operational. | | | | Reentry
2015-06-28. Was operational. | | | | Reentry
2015-08-23. Was operational. | | | | Reentry
2015-09-07. Was operational. | | | | Reentry
2015-09-29. Was operational. | | | | Returned
to Earth. Aboard Dragon SpX-5 | | | | Returned
to Earth. Aboard Dragon SpX-5 | | | | Reentry
2015-01-07. Was operational. | | | | Reentry
2014-12-13. Was operational. | | | | Reentry
2015-03-04. Was operational. | | | | Reentry
2015-01-16. Was operational. | | | | Returned
to Earth. Aboard Dragon SpX-5 | | | | Returned
to Earth. Aboard Dragon SpX-5 | | | | Reentry
2015-10-12. Was operational. | | | | Reentry
2015-10-03. Was operational. | | | | Reentry
2015-03-03. Was operational. | | | | Reentry
2015-03-15. Was operational. | | | | Reentry
2015-02-01. Was operational. | | | | Reentry
2014-12-14. Was operational. | | | | Reentry
2015-10-14. Was operational. | | | | Reentry
2015-08-07. Was operational. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reentry
2015-10-13. Was operational. | | | | Reentry
2015-12-27. Was operational. | | | | Reentry
2016-05-18. Was operational. | | | | Reentry
2016-03-05. Was operational. | | | | Reentry
2016-05-29. Was operational. | | | | Reentry
2016-06-24. Was operational. | | | | Reentry
2016-06-20. Was operational. | | | | Reentry
2016-07-21. Was operational. | | | | Reentry
2016-07-17. Was operational. | | | | Reentry
2016-06-22. Was operational. | | | | Reentry
2016-02-08. Was operational. | | | | Reentry
2016-08-09. Was operational. | | | | Reentry
2016-08-09. Was operational. | | | | Reentry
2016-08-09. Was operational. | | | | Reentry
2016-08-24. Was operational. | | | | Reentry
2016-07-31. Was operational. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reentry
2016-09-22. Was operational. | | | | Reentry
2016-10-02. Was operational. | | | | Reentry
2016-10-14. Was operational. | | | | Reentry
2016-10-17. Was operational. | | | | Reentry
2016-09-25. Was operational. | | | | Reentry
2016-08-22. Was operational. | | | | Reentry
2016-09-21. Was operational. | | | | Reentry
2016-05-22. Was operational. | | | | Reentry
2016-10-16. Was operational. | | | | Reentry
2016-10-12. Was operational. | | | | Returned
to Earth. Aboard Dragon SpX-8? | | | | Returned
to Earth. Aboard Dragon SpX-8? | | | | Reentry
2016-10-11. Was operational. | | | | Reentry
2016-09-12. Was operational. | | | | Reentry
2018-06-16. Was operational. | | | | Reentry
2018-01-23. Was operational. | | | | Reentry
2018-04-05. Was operational. | | | | Reentry
2018-03-11. Was operational. | | | | Reentry
2018-08-14. Was operational. | | | | Reentry
2018-02-12. Was operational. | | | | Reentry
2018-04-07. Was operational. | | | | Reentry
2017-07-25. Was operational. | | | | Reentry
2017-12-25. Was operational. | | | | Reentry
2018-02-28. Was operational. | | | | Reentry
2018-03-04. Was operational. | | | | Reentry
2018-03-04. Was operational. | | | | Reentry
2018-04-15. Was operational. | | | | Reentry
2017-12-01. Was operational. | | | | Reentry
2018-04-18. Was operational. | | | | Reentry
2017-11-08. Was operational. | | | | Reentry
2018-06-27. Was operational. | | | | Reentry
2018-04-05. Was operational. | | | | Reentry
2017-10-03. Was operational. | | | | Reentry
2018-04-05. Was operational. | | | | Reentry
2018-03-12. Was operational. | | | | Reentry
2018-02-17. Was operational. | | | | Reentry
2018-03-11. Was operational. | | | | Reentry
2018-02-28. Was operational. | | | | Reentry
2018-06-03. Was operational. | | | | Reentry
2018-10-25. Was operational. | | | | Reentry
2018-11-10. Was operational. | | | | Reentry
2018-06-01. Was operational. | | | | Reentry
2018-06-26. Was operational. | | | | Reentry
2018-11-07. Was operational. | | | | Reentry
2018-05-12. Was operational. | | | | Reentry
2018-09-22. Was operational. | | | | Reentry
2022-11-16. Was operational? | | | | Reentry
2023-01-16. Was operational | | | | Reentry
2023-03-28. Was operational | | | | Reentry
2022-12-22. Was operational? | | | | Reentry
2022-12-13. Was operational? | | | | Reentry
2023-01-08. Was operational | | | | Reentry
2022-11-29. Was operational? | | | | Reentry
2023-03-28. Was operational | | | | Reentry
2023-03-20. Was operational | | | | Reentry
2023-03-06. Was operational | | | | Reentry
2022-10-20. Was operational? | | | | Reentry
2023-01-13. Was operational | | | | Reentry
2022-11-08. Was operational? | | | | Reentry
2023-01-25. Was operational? | | | | Reentry
2023-03-20. Was operational? | | | | Reentry
2023-01-15. Was operational? | | | | Reentry
2022-12-07. Was operational? | | | | Reentry
2022-12-08. Was operational? | | | | Reentry
2022-10-28. Was operational? | | | | Reentry
2023-03-22. Was operational? | | | | Reentry
2023-01-27. Was operational? | | | | Reentry
2023-01-06. Was operational? | | | | Reentry
2023-01-08. Was operational? | | | | Reentry
2023-01-13. Was operational | | | | Reentry
2022-12-28. Was operational? | | | | Reentry
2023-02-08. Was operational? | | | | Reentry
2023-01-16. Was operational? | | | | Reentry
2023-01-27. Was operational? | | | | Reentry
2022-11-16. Was operational? | | | | Reentry
2022-11-29. Was operational? | | | | Reentry
2022-12-13. Was operational? | | | | Reentry
2023-03-07. Was operational? | | | | Reentry
2023-01-07. Was operational? | | | | Reentry
2022-12-14. Was operational? | | | | Reentry
2023-01-18. Was operational? | | | | | | | | Reentry
2023-01-10. Was operational? | | | | Reentry
2022-12-07. Was operational? | | | | Reentry
2022-12-30. Was operational? | | | | Reentry
2023-02-03. Was operational? | | | | Reentry
2022-12-21. Was operational? | | | | Reentry
2023-02-17. Was operational until 2017-02-XX. Retired. (Planet has 100%
record of contacting satellites that have been deployed on-orbit, but 2 (not
known which ones exactly) were retired (became non-responsive) out of
Flock-3p) | | | | Reentry
2023-02-28. Was operational until 2017-02-XX. Retired. (Planet has 100%
record of contacting satellites that have been deployed on-orbit, but 2 (not
known which ones exactly) were retired (became non-responsive) out of
Flock-3p) | | | | Reentry
2023-01-21. Was operational? | | | | Reentry
2023-03-22. Was operational? | | | | Reentry
2023-02-14. Was operational? | | | | Reentry
2023-01-27. Was operational? | | | | Reentry
2023-01-25. Was operational? | | | | Reentry
2022-12-13. Was operational? | | | | Reentry
2023-01-10. Was operational? | | | | Reentry
2023-02-07. Was operational? | | | | Reentry
2023-03-14. Was operational? | | | | Reentry
2022-12-19. Was operational? | | | | Reentry
2023-02-08. Was operational? | | | | Reentry
2023-02-12. Was operational? | | | | Reentry
2023-02-28. Was operational? | | | | Reentry
2023-01-04. Was operational? | | | | Reentry
2023-02-28. Was operational? | | | | Reentry
2023-01-16. Was operational? | | | | Reentry
2023-01-31. Was operational? | | | | Reentry
2023-02-03. Was operational? | | | | Reentry
2023-01-20. Was operational? | | | | Reentry
2023-02-20. Was operational? | | | | Reentry
2023-01-03. Was operational? | | | | Reentry
2022-12-14. Was operational? | | | | Reentry
2023-02-07. Was operational? | | | | Reentry
2023-01-27. Was operational? | | | | Reentry
2022-12-28. Was operational? | | | | Reentry
2023-01-14. Was operational? | | | | Reentry
2023-01-03. Was operational? | | | | Reentry
2022-12-29. Was operational? | | | | Reentry
2023-03-07. Was operational? | | | | Reentry
2023-02-03. Was operational? | | | | Reentry
2022-12-28. Was operational? | | | | Reentry
2023-01-28. Was operational? | | | | Reentry
2023-01-20. Was operational? | | | | Reentry
2023-01-20. Was operational? | | | | Reentry
2023-01-31. Was operational? | | | | Reentry
2022-12-28. Was operational? | | | | Reentry
2023-02-21. Was operational? | | | | Reentry
2023-01-27. Was operational? | | | | Reentry
2023-03-20. Was operational? | | | | Reentry
2022-12-31. Was operational? | | | | Reentry
2023-01-19. Was operational? | | | | Reentry
2022-11-29. Was operational? | | | | Reentry
2023-03-29. Was operational? | | | | Reentry
2023-01-07. Was operational? | | | | Reentry
2023-02-07. Was operational? | | | | Reentry
2023-02-18. Was operational? | | | | Reentry
2022-12-04. Was operational? | | | | Reentry
2023-02-07. Was operational? | | | | Reentry
2023-02-13. Was operational? | | | | Reentry
2023-02-07. Was operational? | | | | Reentry
2022-12-22. Was operational? | | | | Reentry
2023-02-07. Was operational? | | | | Reentry
2023-02-18. Was operational? | | | | Reentry
2022-12-28. Was operational? | | | | Reentry
2023-02-16. Was operational? | | | | Reentry
2023-02-28. Was operational? | | | | Reentry
2023-01-06. Was operational? | | | | Reentry
2022-03-17. Was operational. | | | | Reentry
2022-05-21. Was operational. | | | | Reentry
2022-05-31. Was operational. | | | | Reentry
2022-05-17. Was operational. | | | | Reentry
2022-04-07. Was operational. | | | | Reentry
2022-05-09. Was operational. | | | | Reentry
2022-06-15. Was operational. | | | | Reentry
2022-03-25. Was operational. | | | | Reentry
2022-05-01. Was operational. | | | | Reentry
2022-06-24. Was operational. | | | | Reentry
2022-04-24. Was operational. | | | | Reentry
2022-06-20. Was operational. | | | | Reentry
2022-03-06. Was operational. | | | | Reentry
2022-04-20. Was operational. | | | | Reentry
2022-09-02. Was operational? | | | | Reentry
2022-04-19. Was operational. | | | | Reentry
2022-03-26. Was operational. | | | | Reentry
2022-07-08. Was operational. | | | | Reentry
2022-08-23. Was operational? | | | | Reentry
2022-04-06. Was operational. | | | | Reentry
2022-06-06. Was operational. | | | | Reentry
2022-01-25. Was operational. | | | | Reentry
2022-04-13. Was operational. | | | | Reentry
2022-03-29. Was operational. | | | | Reentry
2022-06-09. Was operational. | | | | Reentry
2022-04-04. Was operational. | | | | Reentry
2022-03-24. Was operational. | | | | Reentry
2022-07-11. Was operational. | | | | Reentry
2022-06-25. Was operational. | | | | Reentry
2022-07-07. Was operational. | | | | Reentry
2022-05-22. Was operational. | | | | Reentry
2022-08-19. Was operational? | | | | Reentry
2022-01-14. Was operational. | | | | Reentry
2022-04-04. Was operational. | | | | Reentry
2022-06-17. Was operational. | | | | Reentry
2022-03-22. Was operational. | | | | Reentry
2022-06-13. Was operational. | | | | Reentry
2022-04-02. Was operational. | | | | Reentry
2022-08-21. Was operational? | | | | Reentry
2022-08-28. Was operational? | | | | Reentry
2022-05-31. Was operational. | | | | | | | | Reentry
2022-09-19. Was operational? | | | | Reentry
2022-05-17. Was operational. | | | | Reentry
2022-06-23. Was operational. | | | | Reentry
2022-04-16. Was operational. | | | | Reentry
2022-04-27. Was operational. | | | | Reentry
2022-04-06. Was operational. | | | | Reentry
2023-03-24. Was operational | | | | Reentry
2023-03-29. Was operational | | | | Reentry
2023-04-04. Was operational | | | | Reentry
2023-02-28. Was operational | | | | Reentry
2023-03-28. Was operational | | | | | | | | | | | | | | | | Reentry
2022-11-01. Was operational? | | | | Reentry
2022-10-29. Was operational? | | | | Reentry
2022-12-28. Was operational? | | | | Reentry
2022-12-02. Was operational? | | | | Reentry
2022-12-02. Was operational? | | | | Reentry
2022-11-08. Was operational? | | | | Reentry
2022-11-19. Was operational? | | | | Reentry
2022-11-29. Was operational? | | | | Reentry
2022-11-08. Was operational? | | | | Reentry
2022-12-05. Was operational? | | | | Reentry
2022-11-29. Was operational? | | | | Reentry
2022-01-14. Was operational? | | | | Reentry
2022-10-22. Was operational? | | | | Reentry
2022-10-14. Was operational | | | | Reentry
2022-12-15. Was operational? | | | | Reentry
2022-12-14. Was operational? | | | | | | | | | | | | | | | | Reentry
2023-02-14. Was operational | | | | Reentry
2023-02-23. Was operational | | | | Reentry
2023-01-21. Was operational | | | | Reentry
2022-12-29. Was operational | | | | Reentry
2023-01-03. Was operational | | | | Reentry
2023-02-20. Was operational | | | | Reentry
2023-01-14. Was operational | | | | Reentry
2023-01-17. Was operational | | | | Reentry
2023-01-31. Was operational | | | | Reentry
2023-01-04. Was operational | | | | Reentry
2023-02-28. Was operational | | | | Reentry
2023-02-14. Was operational | | | | Reentry
2023-04-13. Was operational | | | | | | | | | | | | Reentry
2023-05-17. Was operational | | | | Reentry
2023-03-15. Was operational | | | | | | | | Reentry
2023-04-08. Was operational | | | | Reentry
2023-05-06. Was operational | | | | Reentry
2023-05-16. Was operational | | | | | | | | | | | | Reentry
2023-04-26. Was operational | | | | | | | | Reentry
2023-05-09. Was operational | | | | Reentry
2023-05-04. Was operational | | | | Reentry
2023-05-16. Was operational | | | | Reentry
2023-03-14. Was operational | | | | Reentry
2023-04-15. Was operational | | | | Reentry
2023-03-15. Was operational | | | | Reentry
2023-04-08. Was operational | | | | Reentry
2023-04-19. Was operational | | | | | | | | Reentry
2023-04-29. Was operational | | | | Reentry
2023-05-16. Was operational | | | | | | | | | | | | | | | | | | | | | | | | Reentry
2023-05-02. Was operational | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Flock-4e' 1 (SuperDove, FLOCK 4 EP 1) | | | | Flock-4e' 2 (SuperDove, FLOCK 4 EP 2) | | | | Flock-4e' 3 (SuperDove, FLOCK 4 EP 3) | | | | Flock-4e' 4 (SuperDove, FLOCK 4 EP 4) | | | | Flock-4e' 5 (SuperDove, FLOCK 4 EP 5) | | | | Flock-4e' 6 (SuperDove, FLOCK 4 EP 6) | | | | Flock-4e' 7 (SuperDove, FLOCK 4 EP 7) | | | | Flock-4e' 8 (SuperDove, FLOCK 4 EP 8) | | | | Flock-4e' 9 (SuperDove, FLOCK 4 EP 9) | | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | Operational
(Official confirmation for all 40 spacecraft) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | | | Operational
(Twitter post about 100% record of contact maintained on 2023-01-05 last
checked 2023-04-15) | | |
|