510(k) Report

510(k) · Cleared

Cleared

Caspian Spinal System

K092640510(k) SpecialCleared Nov 6, 200971-day reviewClass II21 CFR 888.3070

Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly, last Nov 3, 2026

K2m, Inc. · MNI Orthosis, Spinal Pedicle Fixation

Cleared on Nov 6, 2009 after a 71-day review. The FDA summary names its predicate without a number. 47 later devices descend from it.

Decided
Nov 6, 2009
Review
71 days
Class
Class II
Product code
MNI
Recalls
None
Predicates
0

47 later devices descend from it, 3 citing it directly.

Descendants, by year cleared 2014: 7 descendants cleared2012: 2 descendants cleared2011: 1 descendant cleared2013: 2 descendants cleared2015: 6 descendants cleared2018: 6 descendants cleared2026: 2 descendants cleared2024: 7 descendants cleared2017: 2 descendants cleared2025: 1 descendant cleared2016: 4 descendants cleared2022: 2 descendants cleared2021: 1 descendant cleared2023: 3 descendants cleared2020: 1 descendant cleared20052010201520202025
  1. This deviceK092640 Caspian Spinal SystemK2m, Inc. · 2009
  2. Descendant · cites it directly · 46 of its ownK103232 Caspian Spinal SystemK2m, Inc. · 2011
  3. Descendant · 2 generations on · 43 of its ownK120656 Everest Spinal SystemK2m, Inc. · 2012
  4. Descendant · 3 generations on · 41 of its ownK132757 Everest Spinal SystemK2m, Inc. · 2013
  5. Descendant · 3 generations on · 34 of its ownK132361 Everest Spinal SystemK2m, Inc. · 2013
  6. Descendant · 3 generations on · 33 of its ownK133944 Range, Spinal System, Everest Spinal SystemK2m, Inc. · 2014

Showing 5 of 47 descendants. See all descendants

Descendants cleared per year

2011: 12012: 22013: 22014: 72015: 62016: 42017: 22018: 62020: 12021: 12022: 22023: 32024: 72025: 12026: 2
2011high 7 (2014) · low 0 (2019)2026

Most influential descendants

Showing 5 of 47 · See all
  • K103232Caspian Spinal SystemK2m, Inc. · 2011 · cites it directly46descendants
  • K120656Everest Spinal SystemK2m, Inc. · 2012 · 2 generations on43descendants
  • K132757Everest Spinal SystemK2m, Inc. · 2013 · 3 generations on41descendants
  • K132361Everest Spinal SystemK2m, Inc. · 2013 · 3 generations on34descendants
  • K133944Range, Spinal System, Everest Spinal SystemK2m, Inc. · 2014 · 3 generations on33descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
0 (this device)K092640Caspian Spinal SystemK2m, Inc.2009—
+1K103232Caspian Spinal SystemK2m, Inc.2011—
+2K120656Everest Spinal SystemK2m, Inc.2012—
+3K132757Everest Spinal SystemK2m, Inc.2013—
+3K132361Everest Spinal SystemK2m, Inc.2013—
+3K133944Range, Spinal System, Everest Spinal SystemK2m, Inc.2014—

Descendants by year cleared

Year clearedDevicesWith a Class I recall
201110
201220
201320
201470
201560
201640
201720
201860
202010
202110
202220
202330
202470
202510
202620
FIG. 1 — Lineage of K092640, 2009–2026Source: FDA 510(k) summaries, read by 510(k) Report · How lineage is built

Get the monthly Device Review Tracker

Notable FDA decisions, review times and new Class I recalls. See an issue.

Sources: FDA 510(k) database (decision fields), the FDA summary (predicates and indications), FDA recall and enforcement reports, and MAUDE; processed by 510(k) Report. Verify on FDA.gov · Methodology and accuracy.

Planning a device in MNI? A 510(k) Report weighs predicate choices, recall history and review times for a new device like this one.

  • Candidate predicates for a device like this, rankedin the report
  • Recall history across each candidate’s familyin the report
Get a 510(k) Report

What was it cleared against? (2)

Devices the submitter claimed this one is substantially equivalent to (*), and reference devices cited for a specific test or feature (†), as written in the FDA summary.

TypeNumberDeviceApplicantDecidedRecalls
*—Synthes Starlock/Cervifix
Named without a submission number
—
*—DePuy Mountaineer
Named without a submission number
—

What descends from it? (47)

See all 47

3 later devices cite it directly; ranked here by how many devices descend from each in turn.

NumberDeviceApplicantDecidedDescendants
K103232Caspian Spinal SystemK2m, Inc.201146
K121808Casian, 3.5/4.5 ConnectorsK2m, Inc.20121
K142558Caspian OCT/MESA Mini/DENALI Mini Spinal SystemK2m20140

Has anything in its family been recalled? (0 Class I)

No FDA recall names this device.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • Of its descendants, K103232 (K2m, Inc., 2011) has gone furthest, with 46 descendants of its own.

How does its category compare?

All MNI devices

MNI Orthosis, Spinal Pedicle Fixation: FDA decisions, review times, recalls and adverse event reports over 20 years. 2009, this device’s year, is highlighted.

FDA decisions per year · MNI

1in 2017

2007: 202008: 232009: 182010: 162011: 172012: 192013: 142014: 62015: 122016: 72017: 1
2007high 23 (2008) · low 0 (2018)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · MNI

168in 2016

2007: 82 days median2008: 64 days median2009: 86 days median2010: 74 days median2011: 111 days median2012: 75 days median2013: 77 days median2014: 104 days median2015: 54 days median2016: 168 days median
2007high 168 (2016) · low 54 (2015)2026

Receipt to decision; years with fewer than 3 clearances left blank.

Recalls per year · MNI

1in 2018

2007: 262008: 82009: 32010: 12012: 12013: 42015: 12018: 1
2007high 26 (2007) · low 0 (2011)2026

Class I (0 since 2007) Class II/III not classified

Adverse event reports per year · MNI

80in 2025

2007: 832008: 1082009: 1382010: 1262011: 1462012: 2002013: 8242014: 3012015: 2602016: 1172017: 2472018: 1342019: 1882020: 1152021: 2702022: 2142023: 1222024: 1142025: 80
2007high 824 (2013) · low 80 (2025)2025

MAUDE reports naming product code MNI, not matched to any one device; reports are not rates.

View these four charts as a table
YearDecisionsMedian 510(k) review, daysRecalls (Class I)MAUDE reports
200720822683
200823648108
200918863138
201016741126
2011171110146
201219751200
201314774824
201461040301
201512541260
201671680117
20171—0247
20180—1134
20190—0188
20200—0115
20210—0270
20220—0214
20230—0122
20240—0114
20250—080
20260—0—

What is it indicated for?

The Caspian Spinal System is indicated for the following: DDD (neck pain of discogenic origin with degeneration of the disc as confirmed by patient history and radiographic studies) Spondylolisthesis Spinal stenosis Fracture/dislocation Revision of previous cervical spine surgery Tumors The implants are intended to provide stabilization as an adjunct to fusion when used with autogenous bone graft or allograft following the reduction of…

Read the full statement (136 words)

The Caspian Spinal System is indicated for the following:

DDD (neck pain of discogenic origin with degeneration of the disc as confirmed by patient history and radiographic studies)

Spondylolisthesis

Spinal stenosis

Fracture/dislocation

Revision of previous cervical spine surgery

Tumors

The implants are intended to provide stabilization as an adjunct to fusion when used with autogenous bone graft or allograft following the reduction of fractures/dislocations or trauma in the spine.

The rod and hook components are intended for use in the cervical/upper thoracic (C1-T3) spine. The pedicle screws are limited to placement in T1-T3 in treating thoracic conditions only. The pedicle screws are not intended to be placed in or treat conditions involving the cervical spine.

The Caspian Spinal System can also be linked to the Range Spinal System using the 3.5mm/5.5mm rod connectors or transitional rods.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K092640: Caspian Spinal System.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 4, 2026. https://510kreport.com/device/K092640

Report an extraction error

Tell us what is wrong; we check it against the FDA summary.

Are you the manufacturer?

Send a correction or an update to this page, for example a newer model or a public statement about a recall.

Record history
  • FDA decision record loaded May 2, 2026
  • Summary read Oct 13, 2026 (extraction version 9eaa42aa01ed)
  • Lineage and recalls computed Nov 3, 2026
  • Page last updated Nov 3, 2026