What is a true knot in the umbilical cord?
A true knot in the umbilical cord is an actual knot tied in the cord itself (as opposed to a “false knot,” which is only a harmless bulge of blood vessels), and in most cases it stays loose and causes no harm. The distinction matters, because a true knot can, if it tightens, compress the vessels running through the cord and interrupt the baby’s oxygen supply. But it is worth being clear about how these behave: the majority of true knots remain loose throughout pregnancy and delivery, and most babies with a true knot are born healthy.
This is one of the four conditions under our hub on problems with the umbilical cord. What makes the true knot distinctive (and difficult from both a medical and a legal standpoint) is that it is largely unpredictable and very hard to see before birth.
How and why they form
True knots form when the baby passes through a loop of its own cord, usually early in pregnancy when the baby is small and there is ample room to move. Factors associated with a higher chance of a true knot include a long umbilical cord, excess amniotic fluid (polyhydramnios), a smaller baby with more room to move, monoamniotic twins sharing a sac, and prior pregnancies. They are found in roughly 1 in 100 to 1 in 200 births. None of these factors makes a knot preventable; they simply describe the circumstances in which knots are somewhat more likely.
Why true knots are hard to detect
We want to be candid about this, because it is central to understanding these cases: true knots are notoriously difficult to detect before birth. On a standard ultrasound, a knot is easy to miss and is often confused with the normal loops and folds of the cord. Even with color Doppler, which shows blood flow, a true knot is identified only some of the time, and it is frequently discovered only after delivery when the cord is examined. There is no routine screening that reliably finds true knots, and no guideline recommends looking for them in a low-risk pregnancy. This detection limit is real, and any candid discussion of a true-knot case has to start from it.
Did the fetal monitoring show a baby in trouble that wasn’t acted on? Because a true knot is hard to detect in advance, these cases usually turn on how the team responded to distress during labor. Our attorneys review the monitoring records with you at no cost.
When a true knot causes harm
A true knot becomes dangerous when it tightens (most often as the baby descends during labor, or with fetal movement) enough to compress the cord’s vessels and choke off blood flow. When that happens, the baby can be deprived of oxygen, and the result can be asphyxia and hypoxic-ischemic encephalopathy (HIE), which can lead to cerebral palsy and, in the most severe cases, stillbirth. As with other cord problems, the way this trouble announces itself is on the fetal heart-rate monitor: a tightening knot produces the same decelerations and, in serious cases, sustained abnormalities that signal oxygen deprivation.
Monitoring and management
Because a true knot usually cannot be found in advance, the safeguard is the same one that protects against other cord problems: careful monitoring of the baby during labor and a prompt, correct response to signs of distress. When a fetal heart-rate tracing becomes non-reassuring, the standard of care is to interpret it correctly and act: repositioning, oxygen and fluids, reducing labor-stimulating medication, and moving to expedited or emergency delivery if the pattern does not recover. In a case involving a true knot, the legal question is rarely whether the knot was found beforehand (it usually was not, and often could not be) but whether the team responded appropriately once the baby signaled distress.
Was the harm preventable?
A true knot itself is not preventable, and failing to detect one in advance is usually not negligence given the real limits of ultrasound. When harm from a true knot could have been prevented, it is almost always at the stage of response, not detection: a deteriorating fetal tracing that was recognized too late or not acted on, or a delivery that should have been expedited and was not. A fair assessment of one of these cases distinguishes what could not reasonably have been seen from what should have been done once the baby showed it was in trouble.
Legal options for families
A true-knot claim is a medical-negligence claim, and it usually turns on the response to fetal distress rather than on detecting the knot. It asks whether the team recognized and acted on signs that the baby was not getting enough oxygen as the standard of care required — and whether a failure caused lasting harm. Where a baby suffered brain injury, compensation may need to cover a lifetime of care; our HIE settlement amounts page explains how those cases are valued. It can help to understand the related cord conditions, including nuchal cord and vasa previa. Filing deadlines (statutes of limitations) vary by state, so confirm them early.
Where your case would be handled depends on where the care happened. Banville Law attorneys are licensed in New York and Washington, D.C.; The Weitz Firm attorneys are licensed in Pennsylvania and New Jersey. Everywhere else, the alliance connects families with its vetted network of local birth injury attorneys. Special rules apply to care at military or federally funded hospitals.
Frequently asked questions
Can a true knot be seen on ultrasound?
Only sometimes. True knots are difficult to detect before birth and are easily confused with the normal loops of the cord. Even color Doppler identifies them only part of the time, and many are found only after delivery. There is no reliable routine screening for true knots, which is an important limitation.
Does a true knot always harm the baby?
No. The majority of true knots stay loose and cause no harm, and most babies with a true knot are born healthy. A knot becomes dangerous only if it tightens enough to compress the cord and reduce the baby’s oxygen, which shows up as distress on the fetal monitor.
If a true knot can’t be seen, can there still be a case?
Possibly, but usually not for failing to find the knot. These cases generally turn on whether the team recognized and responded to signs of fetal distress during labor. If a deteriorating fetal heart-rate tracing was ignored or a delivery was delayed, that response, rather than the missed detection, is where the claim lies.
What are the signs a true knot is affecting the baby?
The signs are those of oxygen deprivation: an abnormal fetal heart-rate tracing during labor (decelerations, loss of variability, or sustained low heart rate) and, at birth, a depressed baby needing resuscitation, low Apgar scores, or acidosis on cord-blood gases.
Sources
- Hershkovitz R, et al. Risk factors associated with true knots of the umbilical cord. European Journal of Obstetrics & Gynecology and Reproductive Biology. 2001;98(1):36–39.
- Airas U, Heinonen S. Clinical significance of true umbilical knots: a population-based analysis. American Journal of Perinatology. 2002;19(3):127–132.
- Räisänen S, et al. True umbilical cord knot and obstetric outcome. International Journal of Gynecology & Obstetrics. 2013;122(1):18–21.
- American College of Obstetricians and Gynecologists. Intrapartum Fetal Heart Rate Monitoring. Practice Bulletin No. 106. 2009 (reaffirmed).
This page is for general education and is not medical advice. Medical facts above are drawn from the cited primary sources; legal statements reflect the reviewing attorneys’ professional experience. Always consult your physician about medical concerns.