Fiber · Class

LC to SC fiber jumper class

Fiber jumper assemblies can bridge LC and SC connector families while fiber type, polish and optical budget remain separate requirements.

LCend A

SCend B

Bidirectionaldirection evidence

Noneconversion

Endpoint map

Start with what is physically represented

Passive optical jumper direction is not fixed by connector forms.

LC reference →SC reference →Compare references with these ends →Canonical cable/adapter note →

Optical evidence is not yet specified

Connector ends alone do not establish either end’s polish, fiber category, simplex/duplex organization, fiber count or polarity. Read the original class conditions; unknown fields remain unknown.

How to read an optical cable reference →

Capability ledger

Six questions kept separate

DataConditional

Optical path capability depends on fiber type/polish/system.

Evidence: C321A

Power / chargingNot Applicable

No electrical power-delivery role represented.

VideoNot Applicable

No video protocol is inferred from fiber connector forms.

ConversionNone

Connector-form jumper; no media conversion asserted.

Length / reachProduct Specific

Length is exact-jumper specific.

Evidence: C321A

Markings / certificationProduct Specific

Fiber/polish/part markings are exact-jumper facts.

Evidence: C321A

Explicit unknowns

UPC/APC, single-/multimode category, wavelength and optical budget remain unresolved without exact jumper/system evidence.

Source boundary

Why this profile says what it says

Back to first citation ↑

Source records: S370

C321ASource checked · pending review

Corning documents fiber jumper assemblies using LC and SC connector families across multiple optical-fiber constructions; matching LC/SC ends do not establish polish, fiber category, optical budget or live-system safety.

Scope: LC-to-SC jumper-class construction and endpoint context only. · review due 2027-01-05

Corning · Corning PGS176 — Single Mode Optical Fiber Jumper Assemblies with LC or SC Connectors

Generic manufacturer specification supporting keyed LC/SC optical connector interfaces and same-type intermateability to the applicable TIA/EIA-604 interface standard.

Open source ↗

Section 3.1: intermateability and connector keying for LC or SC connector assemblies · This source does not make UPC and APC end faces interchangeable, establish optical power safety, define every fiber type, or provide a universal electrical-style pinout.

Common questions

Questions this record can help resolve

Can LC and SC fiber connect just because an adapter or jumper fits?Separate connector-form mating from fiber type, polish, wavelength, transceiver and optical-budget requirements.

Evidence behind this page

Scope first. Source second. Approval separate.

1 linked sources · 1 scoped claims · 0 sources with inspection/access flags.

Page scope: class

Assessment 2026-10-22 · earliest scheduled source review 2027-01-04. This is a recorded-date assessment, not a live source check. Page-level independent review is not established by this panel.

Inspect 1 source scopes, access limits and dates

S370 · Corning PGS176 — Single Mode Optical Fiber Jumper Assemblies with LC or SC Connectors

Corning · Manufacturer / product-owner domain · inspected 2026-10-06 · due 2027-01-04

Within inspection window

Scoped support: Generic manufacturer specification supporting keyed LC/SC optical connector interfaces and same-type intermateability to the applicable TIA/EIA-604 interface standard.

Not established / limitations: This source does not make UPC and APC end faces interchangeable, establish optical power safety, define every fiber type, or provide a universal electrical-style pinout.

Locator: Section 3.1: intermateability and connector keying for LC or SC connector assemblies

Trace 1 claims to their source records

C321A · P321

Claim scope: LC-to-SC jumper-class construction and endpoint context only.

Source links: S370 · Evidence trail → (private workspace)

Prepare this page for review →Read the evidence method →

Recorded evidence only. An inspection date, publisher label, source link or generated packet is not independent technical review, hardware testing, fabrication approval or a compatibility verdict.